Methods and user interfaces for account recovery

ABSTRACT

The present disclosure generally relates to account recovery. An example method includes, at a computer system in communication with a display generation component and one or more input devices: performing a recovery contact set up process including providing a notification to a contact; after performing the recovery contact set up process, receiving, via the one or more input devices, a request to initiate an account recovery process; in response to the request to initiate the account recovery process and without providing a request to the contact, displaying, via the display generation component, a recovery code interface for receiving a set of recovery credentials; while displaying of the recovery code interface, receiving the set of recovery credentials; in accordance with a determination that the recovery credentials are valid, performing a recovery function; and in accordance with a determination that the recovery credentials are not valid, forgoing performing the recovery function.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. provisional patent applicationNo. 63/197,499, entitled “METHODS AND USER INTERFACES FOR ACCOUNTRECOVERY”, filed Jun. 6, 2021, and U.S. patent application No.63/302,848 entitled “METHODS AND USER INTERFACES FOR ACCOUNT RECOVERY”,filed Jan. 25, 2022 the entire contents of which are hereby incorporatedby reference.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for account recovery.

BACKGROUND

Personal electronic devices are typically protected using one or moreauthentication schemes, such as a password or biometric authentication.In some instances, if a user is unable to satisfy such authenticationschemes, access to such devices or corresponding user accounts can belost.

BRIEF SUMMARY

Some techniques for account recovery using electronic devices, however,are generally cumbersome and inefficient. For example, some existingtechniques use a complex and time-consuming user interface, which mayinclude multiple key presses or keystrokes. As another example, someexisting techniques are insufficient to allow access to accounts whenproper. Accordingly, existing techniques require more time thannecessary and are inadequate, wasting user time and device energy. Thislatter consideration is particularly important in battery-operateddevices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for account recovery. Suchmethods and interfaces optionally complement or replace other methodsfor account recovery. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated computing devices, such methods and interfacesconserve power and increase the time between battery charges, forinstance, by reducing the number of inputs and/or time required suchdevices.

Example methods are described herein. An example method incudes, at acomputer system in communication with a display generation component andone or more input devices: performing a recovery contact set up processincluding providing a notification to a contact; after performing therecovery contact set up process, receiving, via the one or more inputdevices, a request to initiate an account recovery process via thecontact; in response to the request to initiate the account recoveryprocess via the contact and without providing a request to the contact,displaying, via the display generation component, a recovery codeinterface for receiving a set of recovery credentials; while displayingof the recovery code interface, receiving the set of recoverycredentials; in accordance with a determination that the recoverycredentials are valid, performing a recovery function; and in accordancewith a determination that the recovery credentials are not valid,forgoing performing the recovery function.

An example method includes, at a computer system that is incommunication with one or more input devices: receiving, via the one ormore input devices, a request to initiate a process to access an accountof an individual, wherein the process to access the account of theindividual includes: providing an authentication code to another device;and providing a document indicative of a status of the individual to theanother device; in accordance with a determination that a set ofvalidation criteria is satisfied, receiving a credential to access theaccount of the individual wherein the set of validation criteriaincludes a first criterion that is satisfied when the authenticationcode is valid and a second criterion that is satisfied when the documentis valid.

An example method includes, at a computer system in communication with adisplay generation component and one or more input devices: receiving,via the one or more input devices, a set of one or more inputscorresponding to a request to disable an account recovery service for auser account; in response to receiving the set of one or more inputscorresponding to a request to disable the account recovery service,initiating a process for disabling the account recovery service for theuser account, wherein the process for disabling the account recoveryservice for the user account includes: in accordance with adetermination that the user account satisfies a set of service removalcriteria, disabling the account recovery service for the user account;and in accordance with a determination that the user account does notsatisfy the set of service removal criteria, displaying, via the displaygeneration component, a prompt to perform a process for enabling anaccount recovery function for the user account.

An example method includes, at a computer system in communication with adisplay generation component and one or more input devices: afterdisplaying, via the display generation component, data of a first type,receiving, via the one or more input devices, a request to displayrespective data; in response to receiving the request to display therespective data: in accordance with a determination that the request todisplay the respective data satisfies access criteria, displaying therequested respective data; and in accordance with a determination thatthe request to display the respective data does not satisfy the accesscriteria: in accordance with a determination that the request to displaythe respective data is a request to display data of the first type,displaying, via the display generation component, the requestedrespective data; and in accordance with a determination that the requestto display the respective data is not a request to display data of thefirst type, initiating a process to display a first notification on anexternal device for providing the computer system access to therequested respective data.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices and includesinstructions for: performing a recovery contact set up process includingproviding a notification to a contact; after performing the recoverycontact set up process, receiving, via the one or more input devices, arequest to initiate an account recovery process via the contact; inresponse to the request to initiate the account recovery process via thecontact and without providing a request to the contact, displaying, viathe display generation component, a recovery code interface forreceiving a set of recovery credentials; while displaying of therecovery code interface, receiving the set of recovery credentials; inaccordance with a determination that the recovery credentials are valid,performing a recovery function; and in accordance with a determinationthat the recovery credentials are not valid, forgoing performing therecovery function.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with one or more input devicesand includes instructions for: receiving, via the one or more inputdevices, a request to initiate a process to access an account of anindividual, wherein the process to access the account of the individualincludes: providing an authentication code to another device; andproviding a document indicative of a status of the individual to theanother device; in accordance with a determination that a set ofvalidation criteria is satisfied, receiving a credential to access theaccount of the individual wherein the set of validation criteriaincludes a first criterion that is satisfied when the authenticationcode is valid and a second criterion that is satisfied when the documentis valid.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices and includes instructions for:receiving, via the one or more input devices, a set of one or moreinputs corresponding to a request to disable an account recovery servicefor a user account; in response to receiving the set of one or moreinputs corresponding to a request to disable the account recoveryservice, initiating a process for disabling the account recovery servicefor the user account, wherein the process for disabling the accountrecovery service for the user account includes: in accordance with adetermination that the user account satisfies a set of service removalcriteria, disabling the account recovery service for the user account;and in accordance with a determination that the user account does notsatisfy the set of service removal criteria, displaying, via the displaygeneration component, a prompt to perform a process for enabling anaccount recovery function for the user account.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices and includes instructions for:after displaying, via the display generation component, data of a firsttype, receiving, via the one or more input devices, a request to displayrespective data; in response to receiving the request to display therespective data: in accordance with a determination that the request todisplay the respective data satisfies access criteria, displaying therequested respective data; and in accordance with a determination thatthe request to display the respective data does not satisfy the accesscriteria: in accordance with a determination that the request to displaythe respective data is a request to display data of the first type,displaying, via the display generation component, the requestedrespective data; and in accordance with a determination that the requestto display the respective data is not a request to display data of thefirst type, initiating a process to display a first notification on anexternal device for providing the computer system access to therequested respective data.

Example transitory computer-readable storage media are described herein.An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices and includes instructions for:performing a recovery contact set up process including providing anotification to a contact; after performing the recovery contact set upprocess, receiving, via the one or more input devices, a request toinitiate an account recovery process via the contact; in response to therequest to initiate the account recovery process via the contact andwithout providing a request to the contact, displaying, via the displaygeneration component, a recovery code interface for receiving a set ofrecovery credentials; while displaying of the recovery code interface,receiving the set of recovery credentials; in accordance with adetermination that the recovery credentials are valid, performing arecovery function; and in accordance with a determination that therecovery credentials are not valid, forgoing performing the recoveryfunction.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with one or more input devicesand includes instructions for: receiving, via the one or more inputdevices, a request to initiate a process to access an account of anindividual, wherein the process to access the account of the individualincludes: providing an authentication code to another device; andproviding a document indicative of a status of the individual to theanother device; in accordance with a determination that a set ofvalidation criteria is satisfied, receiving a credential to access theaccount of the individual wherein the set of validation criteriaincludes a first criterion that is satisfied when the authenticationcode is valid and a second criterion that is satisfied when the documentis valid.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices and includes instructions for:receiving, via the one or more input devices, a set of one or moreinputs corresponding to a request to disable an account recovery servicefor a user account; in response to receiving the set of one or moreinputs corresponding to a request to disable the account recoveryservice, initiating a process for disabling the account recovery servicefor the user account, wherein the process for disabling the accountrecovery service for the user account includes: in accordance with adetermination that the user account satisfies a set of service removalcriteria, disabling the account recovery service for the user account;and in accordance with a determination that the user account does notsatisfy the set of service removal criteria, displaying, via the displaygeneration component, a prompt to perform a process for enabling anaccount recovery function for the user account.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices and includes instructions for:after displaying, via the display generation component, data of a firsttype, receiving, via the one or more input devices, a request to displayrespective data; in response to receiving the request to display therespective data: in accordance with a determination that the request todisplay the respective data satisfies access criteria, displaying therequested respective data; and in accordance with a determination thatthe request to display the respective data does not satisfy the accesscriteria: in accordance with a determination that the request to displaythe respective data is a request to display data of the first type,displaying, via the display generation component, the requestedrespective data; and in accordance with a determination that the requestto display the respective data is not a request to display data of thefirst type, initiating a process to display a first notification on anexternal device for providing the computer system access to therequested respective data.

Example systems are described herein. An example computer system isconfigured to communicate with a display generation component and one ormore input devices and includes: one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:performing a recovery contact set up process including providing anotification to a contact; after performing the recovery contact set upprocess, receiving, via the one or more input devices, a request toinitiate an account recovery process via the contact; in response to therequest to initiate the account recovery process via the contact andwithout providing a request to the contact, displaying, via the displaygeneration component, a recovery code interface for receiving a set ofrecovery credentials; while displaying of the recovery code interface,receiving the set of recovery credentials; in accordance with adetermination that the recovery credentials are valid, performing arecovery function; and in accordance with a determination that therecovery credentials are not valid, forgoing performing the recoveryfunction.

An example computer system is configured to communicate with one or moreinput devices and includes: one or more processors; and memory storingone or more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for:receiving, via the one or more input devices, a request to initiate aprocess to access an account of an individual, wherein the process toaccess the account of the individual includes: providing anauthentication code to another device; and providing a documentindicative of a status of the individual to the another device; inaccordance with a determination that a set of validation criteria issatisfied, receiving a credential to access the account of theindividual wherein the set of validation criteria includes a firstcriterion that is satisfied when the authentication code is valid and asecond criterion that is satisfied when the document is valid.

An example computer system is configured to communicate with a displaygeneration component and one or more input devices and includes: one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: receiving, via the one or more inputdevices, a set of one or more inputs corresponding to a request todisable an account recovery service for a user account; in response toreceiving the set of one or more inputs corresponding to a request todisable the account recovery service, initiating a process for disablingthe account recovery service for the user account, wherein the processfor disabling the account recovery service for the user accountincludes: in accordance with a determination that the user accountsatisfies a set of service removal criteria, disabling the accountrecovery service for the user account; and in accordance with adetermination that the user account does not satisfy the set of serviceremoval criteria, displaying, via the display generation component, aprompt to perform a process for enabling an account recovery functionfor the user account.

An example computer system is configured to communicate with a displaygeneration component and one or more input devices and includes: one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: after displaying, via the display generationcomponent, data of a first type, receiving, via the one or more inputdevices, a request to display respective data; in response to receivingthe request to display the respective data: in accordance with adetermination that the request to display the respective data satisfiesaccess criteria, displaying the requested respective data; and inaccordance with a determination that the request to display therespective data does not satisfy the access criteria: in accordance witha determination that the request to display the respective data is arequest to display data of the first type, displaying, via the displaygeneration component, the requested respective data; and in accordancewith a determination that the request to display the respective data isnot a request to display data of the first type, initiating a process todisplay a first notification on an external device for providing thecomputer system access to the requested respective data.

An example computer system is configured to communicate with a displaygeneration component and one or more input devices and includes meansfor performing a recovery contact set up process including providing anotification to a contact; means for, after performing the recoverycontact set up process, receiving, via the one or more input devices, arequest to initiate an account recovery process via the contact; meansfor, in response to the request to initiate the account recovery processvia the contact and without providing a request to the contact,displaying, via the display generation component, a recovery codeinterface for receiving a set of recovery credentials; means for, whiledisplaying of the recovery code interface, receiving the set of recoverycredentials; means for, in accordance with a determination that therecovery credentials are valid, performing a recovery function; andmeans for, in accordance with a determination that the recoverycredentials are not valid, forgoing performing the recovery function.

An example computer system is configured to communicate with one or moreinput devices and includes means for receiving, via the one or moreinput devices, a request to initiate a process to access an account ofan individual, wherein the process to access the account of theindividual includes: providing an authentication code to another device;and providing a document indicative of a status of the individual to theanother device; means for, in accordance with a determination that a setof validation criteria is satisfied, receiving a credential to accessthe account of the individual wherein the set of validation criteriaincludes a first criterion that is satisfied when the authenticationcode is valid and a second criterion that is satisfied when the documentis valid.

An example computer system is configured to communicate with a displaygeneration component and one or more input devices, comprising: meansfor receiving, via the one or more input devices, a set of one or moreinputs corresponding to a request to disable an account recovery servicefor a user account; means for, in response to receiving the set of oneor more inputs corresponding to a request to disable the accountrecovery service, initiating a process for disabling the accountrecovery service for the user account, wherein the process for disablingthe account recovery service for the user account includes: inaccordance with a determination that the user account satisfies a set ofservice removal criteria, disabling the account recovery service for theuser account; and in accordance with a determination that the useraccount does not satisfy the set of service removal criteria,displaying, via the display generation component, a prompt to perform aprocess for enabling an account recovery function for the user account.

An example computer system is configured to communicate with a displaygeneration component and one or more input devices, comprising: meansfor, after displaying, via the display generation component, data of afirst type, receiving, via the one or more input devices, a request todisplay respective data; means for, in response to receiving the requestto display the respective data: in accordance with a determination thatthe request to display the respective data satisfies access criteria,displaying the requested respective data; and in accordance with adetermination that the request to display the respective data does notsatisfy the access criteria: in accordance with a determination that therequest to display the respective data is a request to display data ofthe first type, displaying, via the display generation component, therequested respective data; and in accordance with a determination thatthe request to display the respective data is not a request to displaydata of the first type, initiating a process to display a firstnotification on an external device for providing the computer systemaccess to the requested respective data.

Example computer program products are described herein. An examplecomputer program product includes one or more programs configured to beexecuted by one or more processors of a computer system that is incommunication with a display generation component and one or more inputdevices, the one or more programs including instructions for: performinga recovery contact set up process including providing a notification toa contact; after performing the recovery contact set up process,receiving, via the one or more input devices, a request to initiate anaccount recovery process via the contact; in response to the request toinitiate the account recovery process via the contact and withoutproviding a request to the contact, displaying, via the displaygeneration component, a recovery code interface for receiving a set ofrecovery credentials; while displaying of the recovery code interface,receiving the set of recovery credentials; in accordance with adetermination that the recovery credentials are valid, performing arecovery function; and in accordance with a determination that therecovery credentials are not valid, forgoing performing the recoveryfunction.

An example computer program product includes one or more programsconfigured to be executed by one or more processors of a computer systemthat is in communication with one or more input devices, the one or moreprograms including instructions for: receiving, via the one or moreinput devices, a request to initiate a process to access an account ofan individual, wherein the process to access the account of theindividual includes: providing an authentication code to another device;and providing a document indicative of a status of the individual to theanother device; in accordance with a determination that a set ofvalidation criteria is satisfied, receiving a credential to access theaccount of the individual wherein the set of validation criteriaincludes a first criterion that is satisfied when the authenticationcode is valid and a second criterion that is satisfied when the documentis valid.

An example computer program product includes one or more programsconfigured to be executed by one or more processors of a computer systemthat is in communication with a display generation component and one ormore input devices, the one or more programs including instructions for:receiving, via the one or more input devices, a set of one or moreinputs corresponding to a request to disable an account recovery servicefor a user account; in response to receiving the set of one or moreinputs corresponding to a request to disable the account recoveryservice, initiating a process for disabling the account recovery servicefor the user account, wherein the process for disabling the accountrecovery service for the user account includes: in accordance with adetermination that the user account satisfies a set of service removalcriteria, disabling the account recovery service for the user account;and in accordance with a determination that the user account does notsatisfy the set of service removal criteria, displaying, via the displaygeneration component, a prompt to perform a process for enabling anaccount recovery function for the user account.

An example computer program product includes one or more programsconfigured to be executed by one or more processors of a computer systemthat is in communication with a display generation component and one ormore input devices, the one or more programs including instructions for:after displaying, via the display generation component, data of a firsttype, receiving, via the one or more input devices, a request to displayrespective data; in response to receiving the request to display therespective data: in accordance with a determination that the request todisplay the respective data satisfies access criteria, displaying therequested respective data; and in accordance with a determination thatthe request to display the respective data does not satisfy the accesscriteria: in accordance with a determination that the request to displaythe respective data is a request to display data of the first type,displaying, via the display generation component, the requestedrespective data; and in accordance with a determination that the requestto display the respective data is not a request to display data of thefirst type, initiating a process to display a first notification on anexternal device for providing the computer system access to therequested respective data.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for account recovery, thereby increasing the effectiveness,efficiency, and user satisfaction with such devices. Such methods andinterfaces may complement or replace other methods for account recovery.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-6AJ illustrate exemplary user interfaces for recovering accountaccess in accordance with some embodiments.

FIG. 7 is a flowchart of a process for recovering account access inaccordance with some embodiments

FIGS. 8A-8AS illustrate exemplary user interfaces for obtaining accountaccess in accordance with some embodiments.

FIG. 9 is a flowchart of a process for obtaining account access inaccordance with some embodiments.

FIGS. 10A-10Z illustrate exemplary user interfaces for attempting todisable an account recovery service in accordance with some embodiments.

FIG. 11 is a flowchart of a process for attempting to disable an accountrecovery service in accordance with some embodiments.

FIGS. 12A-12K illustrate exemplary user interfaces for managing dataaccess in accordance with some embodiments.

FIG. 13 is a flowchart of a process for managing data access inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for account recovery. For example, computer systems, suchas those described herein may provide a manner in which users can selectcontacts to assist in account recovery when access to user accounts isotherwise precluded. Such techniques can reduce the cognitive burden ona user who implements an account recovery process, thereby enhancingproductivity. Further, such techniques can reduce processor and batterypower otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for account recovery.FIGS. 6A-AJ illustrate exemplary user interfaces for recovering accountaccess. FIG. 7 is a flow diagram illustrating methods of recoveringaccount access in accordance with some embodiments. The user interfacesin FIGS. 6A-AJ are used to illustrate the processes described below,including the processes in FIG. 7 . FIGS. 8A-8S illustrate exemplaryuser interfaces for obtaining account access. FIG. 9 is a flow diagramillustrating methods of obtaining account access in accordance with someembodiments. The user interfaces in FIGS. 8A-8S are used to illustratethe processes described below, including the processes in FIG. 9 . FIGS.10A-10Z illustrate exemplary user interfaces for disabling an accountrecovery service. FIG. 11 is a flow diagram illustrating methods ofattempting to disable an account recovery service in accordance withsome embodiments. The user interfaces in FIGS. 10A-Z are used toillustrate the processes described below, including the processes inFIG. 11 . FIGS. 12A-12K illustrate exemplary user interfaces formanaging data access. FIG. 13 is a flow diagram illustrating methods ofmanaging data access in accordance with some embodiments. The userinterfaces in FIGS. 12A-K are used to illustrate the processes describedbelow, including the processes in FIG. 13 .

The processes described below enhance the operability of the devices andmake the user-device interfaces more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) through various techniques,including by providing improved visual feedback to the user, reducingthe number of inputs needed to perform an operation, providingadditional control options without cluttering the user interface withadditional displayed controls, performing an operation when a set ofconditions has been met without requiring further user input, and/oradditional techniques. These techniques also reduce power usage andimprove battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In addition, in methods described herein where one or more steps arecontingent upon one or more conditions having been met, it should beunderstood that the described method can be repeated in multiplerepetitions so that over the course of the repetitions all of theconditions upon which steps in the method are contingent have been metin different repetitions of the method. For example, if a methodrequires performing a first step if a condition is satisfied, and asecond step if the condition is not satisfied, then a person of ordinaryskill would appreciate that the claimed steps are repeated until thecondition has been both satisfied and not satisfied, in no particularorder. Thus, a method described with one or more steps that arecontingent upon one or more conditions having been met could berewritten as a method that is repeated until each of the conditionsdescribed in the method has been met. This, however, is not required ofsystem or computer readable medium claims where the system or computerreadable medium contains instructions for performing the contingentoperations based on the satisfaction of the corresponding one or moreconditions and thus is capable of determining whether the contingencyhas or has not been satisfied without explicitly repeating steps of amethod until all of the conditions upon which steps in the method arecontingent have been met. A person having ordinary skill in the artwould also understand that, similar to a method with contingent steps, asystem or computer readable storage medium can repeat the steps of amethod as many times as are needed to ensure that all of the contingentsteps have been performed.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. In some embodiments, these terms are used to distinguish oneelement from another. For example, a first touch could be termed asecond touch, and, similarly, a second touch could be termed a firsttouch, without departing from the scope of the various describedembodiments. In some embodiments, the first touch and the second touchare two separate references to the same touch. In some embodiments, thefirst touch and the second touch are both touches, but they are not thesame touch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs (such ascomputer programs (e.g., including instructions)) and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some embodiments, input controller(s) 160 are, optionally,coupled to any (or none) of the following: a keyboard, an infrared port,a USB port, and a pointer device such as a mouse. The one or morebuttons (e.g., 208, FIG. 2 ) optionally include an up/down button forvolume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2 ). In someembodiments, the electronic device is a computer system that is incommunication (e.g., via wireless communication, via wiredcommunication) with one or more input devices. In some embodiments, theone or more input devices include a touch-sensitive surface (e.g., atrackpad, as part of a touch-sensitive display). In some embodiments,the one or more input devices include one or more camera sensors (e.g.,one or more optical sensors 164 and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures and/orair gestures) as input. In some embodiments, the one or more inputdevices are integrated with the computer system. In some embodiments,the one or more input devices are separate from the computer system. Insome embodiments, an air gesture is a gesture that is detected withoutthe user touching an input element that is part of the device (orindependently of an input element that is a part of the device) and isbased on detected motion of a portion of the user's body through the airincluding motion of the user's body relative to an absolute reference(e.g., an angle of the user's arm relative to the ground or a distanceof the user's hand relative to the ground), relative to another portionof the user's body (e.g., movement of a hand of the user relative to ashoulder of the user, movement of one hand of the user relative toanother hand of the user, and/or movement of a finger of the userrelative to another finger or portion of a hand of the user), and/orabsolute motion of a portion of the user's body (e.g., a tap gesturethat includes movement of a hand in a predetermined pose by apredetermined amount and/or speed, or a shake gesture that includes apredetermined speed or amount of rotation of a portion of the user'sbody).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs (such as computer programs(e.g., including instructions)), procedures, or modules, and thusvarious subsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. For example, video player module is,optionally, combined with music player module into a single module(e.g., video and music player module 152, FIG. 1A). In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orcomputer programs (e.g., sets of instructions or including instructions)need not be implemented as separate software programs (such as computerprograms (e.g., including instructions)), procedures, or modules, andthus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. In some embodiments, memory370 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 370 optionally stores additionalmodules and data structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 900,1100 and 1300 (FIGS. 7, 9, 11, 13 ). A computer-readable storage mediumcan be any medium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-AJ illustrate exemplary user interfaces for recovering accountaccess, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 7 .

Generally, implementation of various the techniques for account recoverydescribed below assists a user who is no longer otherwise able to accesstheir user account. In some embodiments, such techniques provide amanner in which a contact of the user account is added as a recoverycontact. Thereafter, access to the user account can be recovered using arecovery code provided by the recovery contact.

FIGS. 6A-6T illustrate techniques for adding a recovery contact for auser account. FIG. 6A illustrates electronic device 600. In FIG. 6A,electronic device 600 is a portable multifunction device and has one ormore components described above in relation to one or more of devices100, 300, and 500.

In FIG. 6A, device 600 displays, on display 602, an account interface604 for a user account of a user Jane Appleseed. The account interface604 is associated with a user account of device 600 in some embodiments.The account interface 604 includes various affordances for configuringfeatures of the user account, including security affordance 606. Inresponse to selection of security affordance 606, device 600 displays asecurity interface. While displaying account interface 604, device 600detects selection of security affordance 606. The selection is a tapgesture 608 on security affordance 606. As shown in FIG. 6B, in responseto detecting tap gesture 608, device 600 displays security interface610.

Security interface 610 includes various affordances for managing accessto the user account and/or data associated with the user account,including account recovery affordance 612. In response to selection ofaccount recovery affordance 612, device 600 displays an account recoveryinterface. While displaying security interface 610, device 600 detectsselection of account recovery affordance 612. The selection is a tapgesture 614 on account recovery affordance 612. As shown in FIG. 6C, inresponse to detecting tap gesture 614, device 600 displays accountrecovery interface 616.

Account recovery interface 616 includes cloud recovery affordance 618and add recovery contact affordance 620. Selection of cloud recoveryaffordance 618 initiates a process for recovering data (e.g., for JaneAppleseed's user account) from a cloud storage environment. In responseto selection of add recovery contact affordance 618, device 600 displaysan initialization interface. While displaying account recovery interface616, device 600 detects selection of add recovery contact affordance620. The selection is a tap gesture 622 on add recovery contactaffordance 606. As shown in FIG. 6D, in response to detecting tapgesture 622, device 600 displays initialization interface 624.

Initialization interface 624 includes information 626 and initializationaffordance 628. Information 626 includes information describing one ormore aspects of selecting a recovery contact and/or using a recoverycontact for account recovery. Information 626 describes, for instance,that a recovery contact can be used to assist in recovering accountaccess.

In response to selection of initialization affordance 628, device 600initiates a recovery contact setup process for adding a recovery contactfor the user account. While displaying initialization interface 624,device 600 detects selection of initialization affordance 628. Theselection is a tap gesture 630 on initialization affordance 628.

In response to detecting tap gesture 630, device 600 initiates biometricauthentication for the user of device 600, as shown in FIG. 6E. In someembodiments, initiating biometric authentication includes obtaining(e.g., capturing with one or more biometric sensors of device 600) datacorresponding to at least a portion of the biometric feature. In FIG.6E, while performing biometric authentication, device 600 displaysbiometric authentication interface 632, which may be overlaid on atleast a portion of initialization interface 624. Biometricauthentication interface 632 includes a biometric authentication glyph,such as biometric authentication glyph 634, to indicate a status of thebiometric authentication (e.g., biometric authentication glyph 634indicates successful biometric authentication).

In response to successful biometric authentication, device 600 displaysrecovery contact selection interface 636, as shown in FIG. 6F. In someembodiments, failure to successfully authenticate prevents display ofinterface 636. Recovery contact selection interface 636 includescandidate contacts 638 (e.g., candidate contacts 638 a, 638 b),selection affordance 640, and continue affordance 642.

Generally, recovery contact selection interface 636 can be used to add arecovery contact for a user account. A candidate contact 638, forexample, can be added as a recovery contact. Candidate contacts are asubset of contacts of device 600, and optionally, determined to betrusted contacts (e.g., contacts designated as family (e.g., immediatefamily), contacts satisfying an age requirement (e.g., 18 years) and/orcontacts sharing a home ecosystem with the user account). In someembodiments, candidate contacts 638 include all trusted contacts ofdevice 600. In other embodiments, candidate contacts 638 include asubset of trusted contacts of device 600.

In the embodiment of FIGS. 6A-6AJ, trusted contacts, when selected as arecovery contact, are automatically added as recovery contacts (e.g.,approval from the selected contact is not required for the contact to beadded as a recovery contact). While displaying recovery contactselection interface 636, device 600 detects a selection of a candidatecontact 638 a (e.g., tap input 644) associated with a contact JohnAppleseed. As shown in FIG. 6G, in response to selection of candidatecontact 638 a, device 600 modifies display of selection indicator 639 toindicate that John Appleseed has been selected.

After modifying display of selection indicator 639, device 600 detects aselection of continue affordance 642. In response to selection ofcontinue affordance 642, device 600 displays a message interface. Whiledisplaying recovery contact selection interface 636, device 600 detectsselection of continue affordance 642. The selection is a tap gesture 646on continue affordance 642. As shown in FIG. 6H, in response todetecting tap gesture 646, device 600 displays message interface 647.

Message interface 647 includes message 648, send affordance 649, andedit affordance 650. Message 648 is a preview of a message notifying theselected contact John Appleseed that they have been added as a recoverycontact. In response to selection of edit affordance 650, device 600allows for message 648 to be edited in message interface 647.

In response to selection of send affordance 649, device 600 opens (e.g.,executes) a messaging application, as shown in FIG. 6I. Opening themessaging application in this manner includes displaying a messageinterface 652 and preloading the messaging application with message 648and recovery contact notification 654.

While displaying message interface 652, device 600 detects selection ofsend affordance 656. The selection is a tap gesture 658 on sendaffordance 656. In response to selection of send affordance 656, device600 provides (e.g., transmits) message 648 to a device of John Appleseedand adds (e.g., automatically adds) John Appleseed as a recovery contactfor Jane Appleseed's user account (recall that adding trusted contactsas recovery contacts does not require approval by the contact).

Further in response to selection of send affordance 656, device 600displays confirmation interface 660. Confirmation interface 660 includesindicator 662 and completion affordance 664. Indicator 662 indicatesthat John Appleseed has been successfully added as a recovery contact.In response to selection of completion affordance 664, device 600terminates (e.g., completes) the recovery contact setup process.

In some embodiments, a contact that is not listed by device 600 as acandidate contact 638 can be selected as a candidate recovery contact.In FIG. 6K, device 600 displays recovery contact selection interface636. While displaying recovery contact selection interface 636, device600 detects selection of selection affordance 640. The selection is atap gesture 668 on account recovery affordance 640. As shown in FIG. 6L,in response to detecting tap gesture 668, device 600 displays contactinterface 670.

Contact interface 670 includes contacts 672 (e.g., contact 670 a,contact 670 b, contact 670 c) and search field 674. Search field 674 canbe used to search contacts of device 600. As shown, search field 674includes a search string “sa”, and a result, contacts of device 600,contacts 672 a-c that include the search string “sa” are displayed. Insome embodiments, contact interface 670 is initially displayed withoutany search string entered in search field 674.

Generally, contact interface 670 may be used to select a contact to beadded as a recovery contact. In some embodiments, only a contact whosedevice satisfies a set of compatibility criteria for device 600 can beselected. In some embodiments, the set of compatibility criteria includea criterion that is met when device 600 and the device of a contactshare a same manufacturer, type, model, and/or software package (e.g.,operating system). In some embodiments, the compatibility criteriainclude a criterion that is met when the device of the contact supportsone or more particular recovery contact features. In some embodiments,the compatibility criteria include a criterion that is met when an ageof a user of the device meets or exceeds a threshold age (e.g., 18years).

Contacts whose devices satisfy the set of compatibility criteria (e.g.,contacts 672 a, 672 c) are displayed in a first manner, while contactswhose devices do not satisfy the compatibility criteria (e.g., contact672 b) are displayed in a second manner. For example, those contactswhose devices do not satisfy the set of compatibility criteria can,optionally, be greyed out, faded, and/or otherwise displayed in a mannersuggesting those contacts are not eligible to be selected as recoverycontacts.

While displaying contact interface 670, device 600 detects selection ofcontact 672 a associated with a contact Sarah Jones. The selection is atap gesture 676 on contact 672 a. As shown in FIG. 6M, in response todetecting tap gesture 622, device 600 displays the name Sarah Jones insearch field 674, indicating that the contact Sarah Jones has beenselected as a recovery contact. Further in response to selection ofcontact 672 a, device 600 removes display of other contacts 672 anddisplays add affordance 678.

As described, if a selected contact is a trusted contact, device 600adds (e.g., automatically adds) the contact as a recovery contactwithout approval from the contact. Accordingly, if Sarah Jones is atrusted contact, in response to selection of add affordance 678, device600 will provide a message for Sarah Jones and add Sarah Jones as arecovery contact, as described above with reference to FIGS. 6H-J.

If a selected contact is not a trusted contact, device 600 adds thecontact as a recovery contact only if the contact approves being addedas a recovery contact. As shown in FIG. 8N, if Sarah Jones is not atrusted contact, in response to selection of add affordance 678, device600 displays message interface 682.

Message interface 682 includes message 684, send affordance 686, andedit affordance 688. Message 684 is a preview of a message requestingthat Sarah Jones approve being added as a recovery contact for the useraccount. In response to selection of edit affordance 654, device 600allows for message 684 to be edited in message interface 682.

In response to selection of send affordance 686, device 600 opens (e.g.,executes) a messaging application, as shown in FIG. 6O. Opening themessaging application in this manner includes displaying a messageinterface 690 of the messaging application and preloading the messagingapplication with message 684 and recovery contact invite 692.

While displaying message interface 682, device 600 detects selection ofsend affordance 694. The selection is a tap gesture 696 on sendaffordance 694. In response to selection of send affordance 694, device600 provides (e.g., transmits) message 684 and recovery contact invite692 to device 600A (FIG. 6P) associated with the selected contact SarahJones. In some embodiments, device 600A includes one or more features ofdevices 100, 300, and/or 500.

In FIG. 6P, device 600A displays, on display 602A, message interface604A of a messaging application (e.g., in response to receiving message684 and/or recovery contact invite 692 from device 600). Messageinterface 604A includes message 684 and recovery contact invite 692.While displaying message interface 604A, device 600A detects selectionof recovery contact invite 692. The selection is a tap gesture 606A onrecovery contact invite 692. As shown in FIG. 6Q, in response todetecting tap gesture 606A, device 600 displays invite interface 608A.

Invite interface 608A includes indicator 610A, indicating that SarahJones has been selected as a recovery contact and that approval isrequired to add Sarah Jones as a recovery contact. Invite interface 608Afurther includes acceptance affordance 612A.

While displaying invite interface 608A, device 600A detects selection ofacceptance affordance 612A. The selection is a tap gesture 614A on theacceptance affordance 612A. In response to selection of the acceptaffordance 612A, device 600A determines if device 600A is secured by apasscode. If device 600A is not secured by a passcode, device 600Adisplays (e.g., overlays on invite interface 608A) passcode interface616A, as shown in FIG. 6R. Passcode interface 616 can be used for entryof a passcode used to secure access to a recovery code for the useraccount of device 600.

Once a passcode has been received by device 600A (or if device 600A wasdetermined to already be secured by a passcode), device 600A sends anindication to device 600 that the request was accepted and displayscompletion interface 620A, as shown in FIG. 6S. Completion interface620A includes indicator 622A and completion affordance 624A. Indicator622A indicates that the request has been accepted, and Sarah Jones hasbeen added as a recovery contact for Jane Appleseed's user account.

While displaying contact interface 620A, device 600A detects selectionof completion affordance 624A. The selection is a tap gesture 626A oncompletion affordance 624A. As shown in FIG. 6T, in response todetecting tap gesture 626A, device 600A displays account recoveryinterface 628A. Account recovery interface 628A includes contactaffordance 630A, indicating that Sarah Jones is a recovery contact forthe user account associated with Jane Appleseed. Account recoveryinterface also includes contact recovery affordance 629A associated witha contact Bob Bailey, a recovery contact for Sarah Jones.

FIGS. 6U-6AG illustrate techniques for accessing a user account using arecovery contact. In FIG. 6U, device 600 displays login interface 632A,which can be used by a user to access a user account by providing avalid set of credentials corresponding to the user account. Logininterface 632A includes forgot password affordance 634A. In response toselection of forgot affordance 634A, device 600 displays a forgotpassword interface. While displaying login interface 632A, device 600detects selection of forgot password affordance 634A. The selection is atap gesture 636A on forgot password affordance 634A. As shown in FIG.6V, in response to detecting tap gesture 636A, device 600 displaysforgot password interface 638A.

Forgot password interface 638A includes account field 640A and continueaffordance 642A. Account field 640A can be used for entry of an accountidentifier associated with the user account to be recovered during anaccount recovery process. In response to selection of continueaffordance 642A, device 600 displays a confirmation interface. Whiledisplaying forgot password interface 638A, device 600 detects selectionof continue affordance 642A. The selection is a tap gesture 644A on thecontinue affordance 642A. As shown in FIG. 6W, in response to detectingtap gesture 644A, device 600 displays confirmation interface 646A.

Confirmation interface 646A includes phone number field 648A andcontinue affordance 650A. Phone number field 648A can be used to verifythe phone number associated with a user account. In response toselection of continue affordance 650A, device 600 displays a recoveryinterface. While displaying confirmation interface 646A, device 600detects selection of continue affordance 650A. The selection is a tapgesture 652A on continue affordance 650A. As shown in FIG. 6X, inresponse to detecting tap gesture 652A, device 600 displays recoveryinterface 654A.

Recovery interface 654A includes indicator 656A and help affordance658A. Indicator 656A indicates that the user account can be accessedusing another device associated with the user account. In response toselection of help affordance 658A, device 600 displays a passcodeinterface. While displaying recovery interface 654A, device 600 detectsselection of help affordance 658A. The selection is a tap gesture 660Aon continue affordance 658A. As shown in FIG. 6Y, in response todetecting tap gesture 658A, device 600 displays (e.g., overlays onrecovery interface 654A) passcode interface 662A.

Passcode interface 662A includes a send code affordance 664A. Inresponse to selection of send code affordance 664A, device 600 causes apasscode to be provided to the phone number entered in number field 648A(FIG. 8W). While displaying passcode interface 662A, device 600 detectsselection of send code affordance 664A. The selection is a tap gesture668A on send code affordance 664A. In response to detecting tap gesture668A, device 600 causes a passcode to be provided (e.g., by text, usinga remote authentication service) to the phone number entered in numberfield 648A.

As shown in FIG. 6Z, further in response to detecting tap gesture 668A,device 600 displays authentication interface 670A. Authenticationinterface 670A includes passcode field 672A and receipt failureaffordance 674A. Passcode field 672A is used for entry of the passcodeprovided in response to selection of send code affordance 664A.Accordingly, a user associated with the user account can, optionally,verify their identity by authenticating on another device associatedwith the user account.

In response to selection of receipt failure affordance 674A, device 600displays a passcode interface. While displaying authentication interface670A, device 600 detects selection of receipt failure affordance 674A.The selection is a tap gesture 676A on help affordance 674A. As shown inFIG. 6AA, in response to detecting tap gesture 676A, device 600 displayspasscode interface 678A.

Passcode interface 678A includes passcode field 680A and help affordance682A. Passcode field 680A is used for entry of a passcode used to secureanother device associated with the user account. In response toselection of help affordance 682A, device 600 displays a help userinterface. While displaying passcode interface 678A, device 600 detectsselection of help affordance 682A. The selection is a tap gesture 684Aon help affordance 682A. As shown in FIG. 6AB, in response to detectingtap gesture 684A, device 600 displays help user interface 686A.

Help user interface 686A includes indicator 688A and ask for helpaffordance 690A. Indicator 688A indicates that a recovery contact canhelp recover access to the user account. In response to selection ofhelp affordance 690A, device 600 initiates a process for requesting helpfrom a recovery contact. While displaying recovery contact helpinterface 686A, device 600 detects selection of help affordance 690A.The selection is a tap gesture 692A on help affordance 690A. As shown inFIG. 6AC, in response to detecting tap gesture 692A, device 600 displaysdevice type interface 694A.

Device type interface 694 includes candidate device types 696, includingcandidate device type 696Aa and candidate device type 696Ab. Candidatedevice type 689Aa is selected to access instructions for generating arecovery code on a phone type or tablet type device of the recoverycontact. Candidate device type 689Ab is selected to access instructionsfor generating a recovery code on a computer type device of the recoverycontact.

While displaying device type interface 694A, device 600 detectsselection of candidate device type 696Aa. The selection is a tap gesture698A on candidate device type 696Aa. As shown in FIG. 6AC, in responseto detecting tap gesture 698A, device 600 displays instructionsinterface 600B.

Instructions interface 600B includes instructions 602B and continueaffordance 604B. Instructions 602B include instructions for generating apasscode on a device of a recovery contact. In response to selection ofcontinue affordance 604B, device 600 initiates a password change processand displays a recovery code interface, such as recovery code interface622B, as described below with respect to FIG. 6AH.

FIGS. 6AE-6AG illustrate a process for providing a recovery code. InFIG. 6AE, device 600A, a smart phone associated with Sarah Jones (e.g.,a recovery contact for Jane Appleseed, the user of device 600 shown inFIG. 6AD), displays account recovery interface 628A including contactaffordance 630A. In some embodiments, the user of device 600A navigatedto user interface 628A after being contacted by Jane Appleseed and beingprovided the instructions shown in FIG. 6AD. In response to selection ofcontact affordance 630A, device 600 displays a recovery managementinterface for the user account associated with contact affordance 630A(e.g., Jane Appleseed). While displaying account recovery interface628A, device 600 detects selection of contact affordance 630A. Theselection is a tap gesture 608B on contact affordance 630A. As shown inFIG. 6AF, in response to detecting tap gesture 608B, device 600Adisplays recovery management interface 610B.

In FIG. 6AF, recovery management interface 610B includes code affordance612B and remove affordance 614B. In response to selection of removeaffordance 614B, device 600A removes Sarah Jones as a recovery contactfor the user account for Jane Appleseed. In response to selection ofhelp affordance 612B, device 600A generates a recovery code that can beused to access the user account for Jane Appleseed. While displayinghelp interface 610B, device 600A detects selection of help affordance612B. The selection is a tap gesture 616B on the help affordance 612B.As shown in FIG. 6AG, in response to detecting tap gesture 616B, device600A displays code generation interface 618B including recovery code620B.

Once a recovery code has been provided using the device of a recoverycontact (e.g., device 600A), the recovery code can in turn be provided(e.g., entered) in a recovery code interface displayed on the deviceperforming the recovery process (e.g., device 600), such as the recoverycode interface 622B of FIG. 6AH, to provide access to the user account.

In FIG. 6AH, device 600, associated with Jane Appleseed, displaysrecovery code interface 622B including a recovery code field 624B and acontinue affordance 626B. Recovery code field 624B is used for entry ofthe recovery code provided by device 600A of recovery contact SarahJones. In some embodiments, device 600A does not directly provide therecovery code to device 600; rather, the user of device 600A (e.g.,Sarah Jones) communicates (e.g., by phone, in person) the code to theuser of device 600. In response to selection of continue affordance626B, device 600 submits the recovery code. While displaying recoverycode interface 622B, device 600 detects selection of continue affordance626B. The selection is a tap gesture 628B on continue affordance 626B.In response to detecting tap gesture 628B, device 600 determines whetherthe recovery code is valid for the user account. In some embodiments,device 600 validates the recovery code using a remote authenticationservice. In some embodiments, device 600 validates the recovery codelocally.

If the recovery code is determined to be valid, device 600 initiates apassword change process including displaying password generationinterface 630B (FIG. 6AI), allowing a user to change a password for theuser account. In some embodiments, if the recovery code cannot bevalidated, the password generation interface 630B is not displayed.

Password generation interface 630B includes new password field 632B,password verification field 634B, and continue affordance 636B. Passwordfield 632B and password verification field 634B can be used for entry ofa new password for the user account. Thereafter, device 600 submits thenew password in response to selection of continue affordance 636B. Whiledisplaying password generation interface 630B, device 600 detectsselection of continue affordance 636B. The selection is a tap gesture638B on continue affordance 636B. As shown in FIG. 6AJ, in response todetecting tap gesture 638, device 600 displays confirmation interface640B indicating that the password for the user account has beensuccessfully changed.

FIG. 7 is a flow diagram illustrating a method recovering account accessusing a computer system in accordance with some embodiments. Method 700is performed at a computer system (e.g., 100, 300, 500, 600) (e.g., asmartphone, a tablet, a computer) that is in communication with adisplay generation component (e.g., a television, a display controller,an internal or external touch-sensitive display system) and one or moreinput devices (e.g., a touch-sensitive surface, a mouse, a keyboard).Some operations in method 700 are, optionally, combined, the orders ofsome operations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 700 provides an intuitive way for recoveringaccount access. The method reduces the cognitive burden on a user forrecovering account access, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to recover account access faster and more efficientlyconserves power and increases the time between battery charges.

The computer system (e.g., 600) performs (702) a recovery contact set upprocess including providing a notification (e.g., 654, 692) to acontact. In some embodiments, the recovery contact set up process is aprocess by which a user of a device selects a contact as a recoverycontact, which can assist in restoring account access for the user. Insome embodiments, the contact is another user of a same device ecosystem(e.g., same device type, same device manufacturer, etc.). In someembodiments, the contact is selected from known contacts (e.g., 638 a-c,672 a-c) of a device of the user (e.g., a contactable user. a deviceassociated with the contactable user). In some embodiments, thenotification is a notification of a first type indicating that thecontact has been added as a recovery contact. In some embodiments, thenotification is a notification of a second type indicating that a userwould like to add the contact as a recovery contact and further includesa request that, when accepted by the contact, allows for the contact tobe added as a recovery contact. In some embodiments, if the contact is atrusted contact (e.g., family member), the notification is anotification of the first type. In some embodiments, if the contact isnot a trusted contact, the notification is a notification of the secondtype. In some embodiments, the notification is provided using amessaging application (e.g., first-party messaging application).

After performing the recovery contact set up process, the computersystem receives (704), via the one or more input devices, a request(e.g., 692A, 604B) to initiate an account recovery process via thecontact. In some embodiments, the request is received during an accountauthentication process (e.g., any process where user identity must beconfirmed, such as a process to change password). In some embodiments,the request includes a set of user inputs (644A, 650A, 658A, 668A, 676A,684A, 692A, 604B) (e.g., one or more user inputs) that navigate througha set of recovery interfaces. In some embodiments, the request includesa selection of a help affordance (e.g., “Ask for help”), which whenselected, causes display of instructions for generating recoverycredentials on the recovery contact's device. In some embodiments, priorto displaying the instructions, the computer system prompts the user toselect a type of the recovery contact's device and the displaysinstructions corresponding to the selected type of the recoverycontact's device.

In response to the request to initiate the account recovery process viathe contact and without providing a request without transmitting arequest, without communicating with the recovery contact) to thecontact, the computer system displays (706), via the display generationcomponent, a recovery code interface (e.g., 622B) (e.g., an interfaceincluding one or more fields for receiving credentials, such as apasscode) for receiving a set of recovery credentials (e.g., 624B)(e.g., passcode generated at recovery contact's device). In someembodiments, the set of recovery credentials can only be used to performthe recovery credentials from the recovery contact interface (e.g., therecovery contact credentials are different than the user's normalauthentication information (e.g., the user's normal password).

While displaying of the recovery code interface, the computer systemreceives (708) the set of recovery credentials.

In accordance with a determination that the recovery credentials arevalid (in some embodiments, and in response to receiving the set ofrecovery credentials) (e.g., the passcode is valid), the computer systemperforms (710) a recovery function (e.g., as shown in FIG. 6AI) (e.g.,initiating a password change process). In some embodiments, the computersystem displays a user interface by which the user can enter a newpassword for his or her account. In some embodiments, once a user hasprovided a valid password entry, the computer system confirms that theuser's password has been changed).

In accordance with a determination that the recovery credentials are notvalid (in some embodiments, and in response to receiving the set ofrecovery credentials), the computer system forgoes (712) performing therecovery function. Providing a user with access to account using arecovery contact provides an additional manner in which a user canquickly and efficiently recover access if the user is otherwise unableto authenticate their identity, which reduces the number of inputsneeded to perform an operation.

In some embodiments, the computer system is associated with a user. Insome embodiments, performing the recovery contact set up processincludes authenticating (e.g., as shown in 6E), via the one or moreinput devices, the user. In some embodiments, during a recovery contactset up process, the computer system authenticates (e.g., biometricallyauthenticates) a user to ensure that only authorized users add recoverycontacts for a user account.

In some embodiments, performing the recovery contact set up processincludes receiving a first user input (e.g., 644, 676) corresponding tothe contact (e.g., 638 a, 672 a) (e.g., an input on an affordancecorresponding to the contact). In some embodiments, performing therecovery contact set up process includes, in response to receiving thefirst user input and in accordance with a determination that the contactis a contact of a first type (e.g., a trusted contact; a contact thathas been identified as a family member of a user of the computer system;a contact that has been designated as an emergency contact), adding(e.g., automatically adding) the contact as a recovery contact. In someembodiments, providing the notification to the contact occurs inresponse to receiving the first user input. In some embodiments, thecomputer system displays an interface from which a user can select arecovery contact from a list of contacts (e.g., recovery contactselection interface, contact interface). In some embodiments, theinterface is displayed in response to a set of inputs, for instance,used to navigate a settings menu. In some embodiments, the interfaceincludes only contacts of the first type. In some embodiments, theinterface includes contacts of the first type and the second type. Insome embodiments, only a subset of contacts of the second type areeligible to be selected as a recovery contact. In some embodiments,contacts of the second type are selectively highlighted based on whetherthey are eligible to be selected as a recovery contact (e.g., ineligiblecontacts are greyed out). In some embodiments, the notification is anotification (e.g., provided via a messaging application) indicatingthat the contact has been added as a recovery contact. In someembodiments, contacts are automatically added as recovery contactsduring the recovery contact set up process if the contact is a trustedcontact of a user. Adding trusted contacts as recovery contacts withoutrequiring approval by the recovery contact allows a user to quickly andefficiently add trustworthy recovery contacts for their account, whichreduces the number of inputs needed to perform an operation.

In some embodiments, providing the notification to the contact includes,in response to the first user input and in accordance with adetermination that the contact is not a contact of the first type (insome embodiments, in accordance with a determination that the contact isa contact of a second type that is different from the first type),providing a request (e.g., 692) to the contact to add the contact as arecovery contact, without adding the contact as a recovery contact inresponse to (e.g., automatically in response to) the first user input.In some embodiments, the notification is a notification (e.g., providedvia a messaging application) requesting that the contact be added as arecovery contact. In some embodiments, contacts are not automaticallyadded as recovery contacts during the recovery contact set up process ifthe contact is not a trusted contact of a user, but rather the contactmust authorize being added as a contact via the request.

In some embodiments, after providing the request to the contact to addthe contact as a recovery contact, the computer system receives, fromthe contact, an approval (e.g., 614A) of the request to add the contactas a recovery contact. In some embodiments, after a user has requestedfor a contact to be a recovery contact, the contact accepts the request,authorizing that the user add the contact as a recovery contact. In someembodiments, the computer system displays a notification indicating thatthe request has been authorized). In some embodiments, in response toreceiving the approval, the computer system adds the contact as arecovery contact.

In some embodiments, performing the recovery contact set up processincludes initiating the recovery contact set up process. In someembodiments, after initiating the recovery contact set up process (e.g.,during the process or after completion of the process), the computersystem displays a recovery settings interface (e.g., 628A). In someembodiments, the recovery setting interface includes a first recoverycontact graphical object (e.g., 630A) (e.g., a user-interactivegraphical object) that corresponds to a first recovery contact that isauthorized to receive the set of recovery credentials for use in therecovery function. In some embodiments, the recovery setting interfaceincludes a first recovery contactee graphical object (e.g., 629A) (e.g.,a user-interactive graphical object) that indicates a second contactthat a user of the computer system is authorized to assist with (e.g.,by providing a second set of recovery credentials for) a second recoveryfunction (e.g., an indication of a contact for which the user is arecovery contact). Displaying an interface with both a recovery contactaffordance and a custodian affordance provides the user with visualfeedback regarding whether the user has selected recovery contactsand/or is a recovery contact for another user, which provides improvedvisual feedback.

In some embodiments, prior to displaying the recovery code interface,the computer system displays, via the display generation component, anauthentication interface (e.g., 670A, 678A) that includes a set of oneor more user-interactive graphical user interface objects (e.g., 672A,680A) (e.g., passcode entry affordances) for authenticating a user ofthe computer system. In some embodiments, the computer system receives afirst set of one or more user inputs that includes a second user input(e.g., an input that corresponds to a “forgot passcode” affordance) thatis received while displaying the authentication interface. In someembodiments, in response to the second user input, a help user interfaceis displayed. In some embodiments, the help user interface includes an“ask for help” affordance and the first set of user inputs includes athird user input corresponding to the “ask for help” affordance and therecovery code interface is displayed in response to the third userinput. In some embodiments, in response to receiving the first set ofone or more user inputs, the computer system ceases to display theauthentication interface, without authenticating a user of the computersystem. In some embodiments, the first set of one or more user inputs isthe request to initiate the account recovery process (e.g., the recoverycode interface is displayed in response to the first set of one or moreuser inputs).

In some embodiments, the authentication interface (e.g., 678A) includesa forgot passcode user-interactive graphical user interface object(e.g., 682A) that, when selected, causes the authentication interface tocease being displayed without authenticating a user of the computersystem. In some embodiments, the second user input (e.g., 684A)corresponds to the forgot passcode user-interactive graphical userinterface object.

In some embodiments, the first set of one or more user inputs includes athird user input (e.g., 692A). In some embodiments, in response to thethird user input, the computer system displays a help user interface(e.g., 686A) that includes an ask for help user-interactive graphicaluser interface object (e.g., 690A). In some embodiments, the third userinput corresponds to the ask for help user-interactive graphical userinterface object. In some embodiments, the recovery code interface isdisplayed in response to the third user input. In some embodiments, therecovery code interface is displayed in response to a subsequent input,received after the third user input, of the first set of one or moreuser inputs.

In some embodiments, the first set of one or more user inputs includes afourth user input (e.g., 698A). In some embodiments, after ceasing todisplay the authentication interface, without authenticating a user ofthe computer system, the computer system displays a plurality of deviceuser-interactive graphical user interface objects (e.g., 696Aa, 696Ab)that corresponds to external electronic devices (e.g., smart phones,personal computers, tablet computers) associated with the contact. Insome embodiments, the fourth user input corresponds to a first deviceuser-interactive graphical user interface object (e.g., 696Aa) of theplurality of device user-interactive graphical user interface objectsthat corresponds to a first external electronic device associated withthe contact.

In some embodiments, in response to the fourth user input, the computersystem displays, in accordance with a determination that the firstexternal electronic device is a device of a first type (e.g., a smartphone), a first set of instructions (e.g., 602B) for providing (e.g.,generating) the set of recovery credentials on the first externalelectronic device. In some embodiments, in response to selection of thefirst device type affordance, the computer system displays a set ofinstructions for providing a set of recovery credentials (e.g., recoverycode) on devices of the first type. In some embodiments, devices of thefirst type include phones, tablets, or other small factor devices.

In some embodiments, in response to the fourth user input, the computersystem displays, in accordance with a determination that the firstexternal electronic device is a device of a second type (e.g., apersonal computer), a second set of instructions (e.g., instructionsthat would be displayed after selecting 696Ab), different from the firstset of instructions, for providing (e.g., generating) the set ofrecovery credentials on the first external electronic device. In someembodiments, in response to selection of the first device typeaffordance, the computer system displays a set of instructions forproviding a set of recovery credentials on devices of the second type.In some embodiments, devices of the first type include personalcomputers, laptops, or other large factor devices. Displayinginstructions that may be used to select a particular device type andsubsequently access instructions relevant to that device type allows auser to quickly and efficiently access instructions for generating arecovery code on a device of a recovery contact, which reduces thenumber of inputs needed to perform an operation.

In some embodiments, the account recovery process is performed for auser account (e.g., as shown in 6AI). In some embodiments, performingthe recovery function includes initiating a password change process forthe user account. In some embodiments, once the computer system hasvalidated the set of recovery credentials, the computer system performsa recovery function, such as initiating a password change process. Insome embodiments, the computer system displays a user interface by whichthe user can enter a new password for their account. In someembodiments, once a user has provided a valid password, the computersystem confirms that the user's password has been changed.

In some embodiments, the computer system (e.g., 600, 600A) receives,from a first external computer system (e.g., 600, 600A), a request(e.g., 692) for the user of the computer system to be added as arecovery contact for the first external computer system. In someembodiments, the request is provided by the first computer system to thesecond computer system via a messaging application. In some embodiments,in response to selection of the request (e.g., in the messagingapplication), the second computer system displays an invite interface(e.g., 608A) including an accept affordance (e.g., 612A), which whenselected, causes the second computer system to approve (e.g., accept)the request to add the user as a recovery contact. In some embodiments,the interface further includes a decline affordance, which whenselected, causes the second computer system to reject the request to addthe user as a recovery contact.

In some embodiments, in response to receiving the request for the userof the computer system to be added as a recovery contact for the firstexternal computer system, the computer system displays (e.g., in aninterface of a messaging application; as part of a text message) anacceptance user-interactive graphical user interface object (e.g.,612A). In some embodiments, the computer system receives a user inputcorresponding to the acceptance user-interactive graphical userinterface object. In some embodiments, in response to receiving the userinput (e.g., 614A) corresponding to the acceptance user-interactivegraphical user interface object, the computer system transmits, to thefirst external computer system, an indication that the request wasaccepted (e.g., an indication that the user of the computer systemaccepted being a recovery contact for the first external computer system(e.g., for an account associated with the first external computersystem.

In some embodiments, after transmitting, to the first external computersystem, the indication that the request was accepted, the computersystem receives a second set of one or more user inputs (e.g., 616B). Insome embodiments, in response to receiving the second set of one or moreuser inputs, providing (e.g., generating, displaying) a second set ofrecovery credentials (e.g., 620B) that, when entered at the firstexternal computer system, enables a second recovery function (e.g., arecovery function for an account associated with the first externalcomputer system).

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7 ) are also applicable in an analogous manner tothe methods described below. For example, method 900 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 700. For example, an authenticationprovided to access an account, as described in method 900, could be acode provided by a recovery contact, as described in method 700. Forbrevity, these details are not repeated below.

FIGS. 8A-8AS illustrate exemplary user interfaces for obtaining accountaccess, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 9 .

Generally, techniques for obtaining account access described belowenable a user associated with a user account to select a contact as abeneficiary of the user account. Thereafter, should a status of the userchange (e.g., the user becomes incapacitated, deceased), the contact, asa beneficiary, can access the user account and/or data associated withthe user account.

FIGS. 8A-8R illustrate techniques for adding a contact as a beneficiary(e.g., trustee) for a user account. In FIG. 8A, device 600 displays, ondisplay 602, security interface 804 associated with a user account for auser Jane Appleseed. In some embodiments, security interface 804 isdisplayed in response to selection of a security affordance of anaccount interface, such as the security affordance 606 of accountinterface 604 (FIG. 6A). Security interface 804 includes variousaffordances for managing access to a user account and/or data associatedwith the user account, including account beneficiary affordance 806. Insome embodiments, in response to selection of account beneficiaryaffordance 806, device 600 displays an account beneficiary interface.While displaying security interface 804, device 600 detects selection ofthe account beneficiary affordance 806. The selection is a tap gesture808 on the account beneficiary affordance 806. As shown in FIG. 8B, inresponse to detecting tap gesture 808, device 600 displays accountbeneficiary interface 810.

Account beneficiary interface 810 includes add beneficiary affordance812. In response to selection of add beneficiary affordance 812, device600 displays an initialization interface. While displaying accountbeneficiary interface 810, device 600 detects selection of addbeneficiary affordance 812. The selection is a tap gesture 814 on addbeneficiary affordance 812. As shown in FIG. 8C, in response todetecting tap gesture 814, device 600 displays initialization interface816.

Initialization interface 816 includes information 818 and initializationaffordance 820. Information 818 includes information describing variousaspects of selecting a contact as a beneficiary. In response toselection of initialization affordance 820, device 600 initiates aprocess for selecting a beneficiary for (e.g., adding a beneficiary to)the user account. While displaying initialization interface 820, device600 detects selection of the initialization affordance 820. Theselection is a tap gesture 822 on the initialization affordance 820.

In response to detecting tap gesture 822, device 600 initiates biometricauthentication, as shown in FIG. 8D. Initiating biometric authenticationincludes obtaining (e.g., capturing with one or more biometric sensorsof the device 600) data corresponding to at least a portion of thebiometric feature. In FIG. 8D, while performing biometricauthentication, device 600 displays biometric authentication interface824, which may be overlaid on at least a portion of the initializationinterface 816. Biometric authentication interface 824 includes abiometric authentication glyph, such as biometric authentication glyph826, to indicate a status of the biometric authentication (e.g.,biometric authentication glyph 826 indicates successful biometricauthentication).

In response to successful biometric authentication, device 600 displaysbeneficiary selection interface 830, as shown in FIG. 8E. Beneficiaryselection interface 830 includes candidate contacts 832 (e.g., candidatecontacts 832 a, 832 b), selection affordance 834, and continueaffordance 836. In some embodiments, if authentication is notsuccessful, device 600 does not display beneficiary selection interface830 and/or requests alternative authentication.

Generally, beneficiary selection interface 830 can be used to select abeneficiary for the user account. A beneficiary can be selected byselecting a candidate contact 832 of beneficiary selection interface830. Candidate contacts are a set of contacts of the user determined tobe trusted contacts (e.g., contacts designated as family (e.g.,immediate family), contacts satisfying an age requirement (e.g., 18years), and/or contacts sharing a home ecosystem with the user). In someembodiments, candidate contacts 832 include all trusted contacts ofdevice 600. In other embodiments, candidate contacts 832 include asubset of trusted contacts of device 600.

While displaying recovery contact selection interface 830, device 600detects a selection of a candidate contact 832 a (e.g., tap input 644)associated with a contact John Appleseed. In some embodiments, inresponse to selection of candidate contact 832 a, device 600 modifiesdisplay of selection indicator 833 to indicate that the user hasselected John Appleseed.

After detecting selection of candidate contact 832 a, device 600 detectsa selection of continue affordance 836. In response to selection ofcontinue affordance 836, device 600 displays a confirmation interface.While displaying beneficiary selection interface 830, device 600 detectsselection of continue affordance 836. The selection is a tap gesture 840on continue affordance 836. As shown in FIG. 8F, in response todetecting tap gesture 840, device 600 displays the confirmationinterface 842, which can be used to confirm selection of a beneficiary,as described below.

A contact can also be selected as a beneficiary using a selectionaffordance, such as selection affordance 834 of FIG. 8E. Whiledisplaying beneficiary selection interface 830, device 600 detectsselection of selection affordance 834. The selection is a tap gesture841 on selection affordance 834. As shown in FIG. 8G, in response todetecting tap gesture 841, device 600 displays contact interface 850.

Contact interface 850 includes contacts 852 and search field 854. Searchfield 854 can be used to search contacts of the user account on device600. As shown, search field 854 includes a search string “jo”, and aresult, contacts of the user account, contacts 854 a-c that include thesearch string “jo”, are displayed. In some embodiments, contactinterface 850 is initially displayed with search field 854 unpopulated.

While displaying contact interface 850, device 600 detects selection ofcontact 852 a associated with contact John Appleseed. The selection is atap gesture 856 on contact 852 a. As shown in FIG. 8H, in response todetecting tap gesture 856, device 600 displays the name John Appleseedin search field 854. Further in response to selection of contact 852 a,device 600 removes display of other contacts 852 and displays addaffordance 858.

While displaying contact interface 850, device 600 detects selection ofadd affordance 858. The selection is a tap gesture 859 on add affordance858. In response to detecting tap gesture 859, device 600 displays aconfirmation interface, such as confirmation interface 842 (FIG. 8F).

In FIG. 8F, confirmation interface 842 includes information 844 andcontinue affordance 846. Information 818 includes information describingone or more privileges provided to a contact when selected as abeneficiary. A beneficiary of a user account receives no additionalprivileges until a status of the user associated with the user accountchanges. If the user associated with the user account passes away, forinstance, the beneficiary for the user account can request access to theuser account and, upon approval of the request, access the user account(e.g., as seen in FIGS. 8S-8AS).

In response to selection of continue affordance 846, a selected contact(e.g., John Appleseed) is added (e.g., stored (e.g., on device 600) as abeneficiary for the account of Jane Appleseed. In some embodiments, aselected contact is added as a beneficiary on device 600 if a device ofthe contact satisfies a set of compatibility criteria for device 600. Insome embodiments, the set of compatibility criteria includes a criterionthat is met when the device of the contact and device 600 share a samemanufacturer, type, model, and/or software package (e.g., operatingsystem). In some embodiments, the set of compatibility criteria includesa criterion that is met when the device of the contact supports one ormore particular beneficiary features. In some embodiments, thecompatibility criteria include a criterion that is met when an age of auser of the device exceeds a threshold age (e.g., 18 years). In someembodiments, a device of a selected contact does not satisfy thecompatibility criteria, the selected contact is not added as abeneficiary on device 600, but still serves as a beneficiary for theuser account (e.g., the selected contact can still obtain access to theuser account and/or is stored as a beneficiary on another device, suchas a server for a beneficiary access service), as described below.

Further in response to selection of continue affordance 846, device 600displays share interface 860, as shown in FIG. 8I. Share interface 860is used to select a manner in which an access key for the user accountis shared with a beneficiary. Share selection interface 860 includesmessage affordance 862 and print affordance 864. Message affordance 862is used to send an access key electronically, for instance, using amessaging application. While displaying share interface 860, device 600detects selection of message affordance 862. The selection is a tapgesture 866 on message affordance. As shown in FIG. 8J, in response todetecting tap gesture 866, device 600 displays message interface 870.

Message interface 870 includes message 872, notification 874, sendaffordance 876, and edit affordance 878. Message 872 is a preview of amessage notifying John Appleseed that they have been added as abeneficiary for the user account. In response to selection of editaffordance 878, device 600 allows for message 872 to be edited inmessage interface 870.

In response to selection of send affordance 876, device 600 opens (e.g.,executes) a messaging application, as shown in FIG. 8K. Opening themessaging application in this manner includes displaying a messageinterface 882 and preloading the messaging application with message 872and beneficiary notification 874.

Beneficiary notification 874 includes an access key for accessing theuser account as a beneficiary. In some embodiments, the manner in whichthe access key is provided is based on whether a device of thebeneficiary satisfies the set of compatibility criteria. If, forexample, a device of a beneficiary satisfies the set of compatibilitycriteria, device 600 includes (e.g., embeds) the access key in thenotification such that receipt of notification causes the access key tobe stored (e.g., automatically stored) in a beneficiary key store(recall that a device of the contact can support one or more beneficiaryfeatures) of the device of the beneficiary. If a device of a beneficiarydoes not satisfy the set of compatibility criteria, the device 600includes a representation of the access key (e.g., an alphanumericrepresentation, an image) in the notification, such as therepresentation 804A (FIG. 8P).

While displaying message interface 882, device 600 detects selection ofsend affordance 884. The selection is a tap gesture 886 on sendaffordance 884. In response to selection of send affordance 884, device600 provides (e.g., transmits) message 872 and notification 874 todevice 890 (FIG. 8L) associated with John Appleseed.

In FIG. 8L, device 890 displays message 872 and notification 874 a inuser interface 890 of a messaging application (e.g., in response toreceiving message 872 and/or notification 874 from device 600). In someembodiments, device 890 includes one or more features of devices 100,300, and/or 500. If device 890 satisfies the set of compatibilitycriteria, device 890 automatically stores an access key included innotification 874 a, for instance, in response to receipt of thenotification 874 a. If device 890 does not satisfy the set ofcompatibility criteria, device 892 does not automatically store theaccess key included in notification 874.

As shown in FIG. 8M, in response to selection of the beneficiarynotification 874 a (e.g., input 892), device 890 displays beneficiaryinterface 894 indicating that the contact has been added as abeneficiary for the user account of Jane Appleseed.

As shown in FIG. 8N, a print affordance of share selection interface860, displayed on device 600 associated with Jane Appleseed, can be usedto provide an access key to a beneficiary manually. While displayingshare selection interface 860, device 600 detects selection of printaffordance 864. The selection is a tap gesture 800A on print affordance864. As shown in FIG. 8O, in response to detecting tap gesture 800A,device 600 displays print interface 802A.

Print interface 802A includes representation 804A, which is arepresentation of an access key. As shown in FIG. 8P, representation804A includes QR (quick response) code 806A and alphanumeric code 808A,each of which can be used as the access key. Print interface 802A can beused to print a copy of the representation 804A; the printed copy canthen be provided to a beneficiary offline, allowing for subsequentaccess to the user account.

Once an access key has been provided (e.g., electronically or manually),device 600 displays completion interface 810A in FIG. 8Q. Completioninterface 810A includes completion affordance 812A. In response toselection of completion affordance 812A (e.g., input 814A), device 600terminates the account beneficiary selection process and displays anaccount beneficiary interface 810, as shown in FIG. 8R. Because JohnAppleseed was successfully added as a beneficiary, account beneficiaryinterface 810 includes affordance 816A associated with John Appleseed.

FIGS. 8S-8AG illustrate processes to access a user account as abeneficiary. FIGS. 8S-8Y illustrate a process to access a user accountusing device 890 that satisfies a set of compatibility criteria ofdevice 600.

In FIG. 8S, device 890 displays account beneficiary interface 820Aassociated with user John Appleseed, the user of device 890. Beneficiaryinterface 820A includes add beneficiary affordance 822A and user accountaffordance 824A. As described, in response to selection of addbeneficiary affordance 822A, device 890 displays an initializationinterface (e.g., FIG. 8C), which is used to initialize a process foradding a beneficiary, as described above.

In FIG. 8S, user account affordance 824A corresponds to the user accountfor Jane Appleseed for which John Appleseed is a beneficiary. Inresponse to selection of user account affordance 824A, device 890displays a beneficiary management interface. While displaying accountbeneficiary interface 820A, device 600 detects selection of the useraccount affordance 824A. The selection is a tap gesture 825A on useraccount affordance 824A. As shown in FIG. 8T, in response to detectingtap gesture 825A, device 890 displays beneficiary management interface826A associated with the user account for Jane Appleseed.

Beneficiary management interface 826A includes request access affordance830A and remove affordance 832A. Remove affordance 832A, when selected,causes device 890 to remove John Appleseed as the beneficiary of theuser account for Jane Appleseed. The request access affordance 830A isused to initiate a process to access the user account for JaneAppleseed. While displaying beneficiary management interface 826A,device 890 detects selection of request access affordance 830A. Theselection is a tap gesture 834A on the request access affordance 830A.As shown in FIG. 8U, in response to detecting tap gesture 834A, device890 displays request access interface 836A.

Request access interface 836A includes information 838A and continueaffordance 840A. Information 838A includes information regarding variousaspects of requesting access as a beneficiary. For example, information838A describes that a request for access must include a document (e.g.,death certificate) indicating a status of a user of the user account forwhich access is being requested (e.g., the user account of JaneAppleseed). While displaying request access interface 836A, device 890detects selection of the continue affordance 840A. The selection is atap gesture 842A on the continue affordance 840A. As shown in FIG. 8V,in response to detecting tap gesture 840A, device 890 displayscertificate interface 844A.

Certificate interface 844A includes upload affordance 846A. In responseto selection of the upload affordance 846A, device 890 provides anupload interface by which a beneficiary can upload the documentindicating a status of the user associated with the user account. Whiledisplaying certificate interface 844A, device 890 detects selection ofthe upload affordance 846A. The selection is a tap gesture 848A on theupload affordance 846A. As shown in FIG. 8W, in response to detectingtap gesture 848A, device 890 displays upload interface 850A.

Upload interface 850A includes select file affordance 852A and uploadaffordance 856A. In response to a selection of select file affordance852A, device 890 provides a process by which a document (e.g., document854A) is selected for inclusion in the access request. In FIG. 8W, theprocess initiated by selection of select file affordance 852A hasalready been used to select document 854A. In the embodiment of FIGS.8S-8AG, the document indicates a status of the user (e.g., JaneAppleseed) of the user account. While displaying upload interface 850A,device 890 detects selection of the upload affordance 856A. Theselection is a tap gesture 858A on the upload affordance 856A. As shownin FIG. 8X, in response to detecting tap gesture 858A, device 890submits the document to a remote access service and displaysconfirmation interface 860A, indicating that the request for access hasbeen submitted.

Confirmation interface 860A includes a completion affordance 862A. Inresponse to selection of completion affordance 862A, device 890 displaysbeneficiary management interface 826A. As shown in FIG. 8Y, because therequest for access has been submitted (and remains pending), device 890replaces display of affordance 830A (FIG. 8T) with indicator 864A toindicate that access has been requested.

In some embodiments, a request for access includes providing both adocument indicating a status of the user of the user account and theaccess key provided to a beneficiary. As described, device 890 is, insome examples, a device satisfying the set of compatibility criteria fordevice 600, and as a result, stores the access key for Jane Appleseed ina beneficiary key store. Accordingly, when providing the access request(e.g., when submitting document 854A), device 890 includes (e.g.,automatically includes) the access key in the request for access (e.g.,without additional user input), ensuring that both the documentindicating status of the user associated with the user account and theaccess key are provided in the access request for the user account.

FIGS. 8Z-AG illustrate an exemplary technique for requesting accessusing device 866A that does not satisfy a set of compatibility criteria.

At FIG. 8Z, device 866A displays, on display 870A, request accessinterface 872A, which can be a user interface of a web browser in someembodiments. In some embodiments, device 866A includes one or morefeatures of devices 100, 300, and/or 500. Request access interface 872Aincludes information 874A and continue affordance 876A.

Information 874A includes information about the process for requestingaccess as a beneficiary. Information 874A describes that a request foraccess must include a document (e.g., death certificate) indicating astatus of a user of the user account and/or an access key for the useraccount. While displaying request access interface 872A, device 866Adetects selection of the continue affordance 876A. The selection is auser input 875A (e.g., mouse click) on the continue affordance 876A. Asshown in FIG. 8AA, in response to user input 875A, device 866A displaysaccount identification interface 880A.

Account identification interface 880A includes account identificationfield 882A and continue affordance 884A. Account identification field882A is used for entry of an identifier (e.g., email or username) of theuser account (e.g., the account associated with Jane Appleseed) to beaccessed by the beneficiary. In some embodiments, account identificationinterface 880A is initially displayed with account identification field882A unpopulated. While displaying account identification interface 880Awith account identification field 882A populated, device 866A detectsselection of the continue affordance 884A. The selection is a user input883A (e.g., mouse click) on the continue affordance 884A. As shown inFIG. 8AB, in response to user input 883A, device 866A displaysbeneficiary information interface 886A.

Beneficiary information interface 886A includes information fields 888Aand continue affordance 890A. In some embodiments, beneficiaryinformation interface 886A is initially displayed with informationfields 888A unpopulated. Information fields 888A are used for entry ofvarious items of personal information associated with the beneficiary(e.g., name, location, date of birth, email, phone number). Whiledisplaying beneficiary information interface 886A with informationfields 888A populated, device 866A detects selection of the continueaffordance 890A. The selection is a user input 891A (e.g., mouse click)on the continue affordance 890A. As shown in FIG. 8AC, in response touser input 891A, device 866A displays beneficiary verification interface894A.

Verification interface 894A includes verification region 896A, which isused to verify one or more items of personal information submitted usingbeneficiary information interface 886A. In some embodiments,verification interface 894A is displayed with verification region 896Aunpopulated. As an example, after selection of continue affordance 890A,a beneficiary receives a passcode (e.g., in an email) which is enteredusing a passcode field 897A of verification region 896A. Verificationregion 896A further includes continue affordance 898A, which is used tosubmit the passcode entered in passcode field 897A. While displayingverification interface 894A with verification region 896A populated,device 866A detects selection of continue affordance 898A. The selectionis a user input 899A (e.g., mouse click) on continue affordance 898A. Asshown in FIG. 8AD, in response to user input 899A and in accordance witha determination that the passcode in passcode 897A is valid, device 866Adisplays key entry interface 804B. In some embodiments, if the passcodeis invalid, key entry interface 804B is not displayed and/or device 866Arequests a valid passcode.

Key entry interface 804B includes key field 806B and continue affordance808B. In some embodiments, key entry interface 804B is displayed withkey field 806B unpopulated. Key field 806B is used for entry of theaccess key for the user account. In some embodiments, key entryinterface 804B does not include key field 806B and instead includes a QRcode scanner (not shown) such that the access key for the user accountis entered by scanning a QR code representation of the access key. Asdescribed, an access key can be provided to a beneficiary electronicallyvia a notification, or optionally, can be printed and provided to thebeneficiary offline (recall that a device that does not meet the set ofcompatibility criteria does not automatically store an access key).While displaying key entry interface 894A with key field 806B populated,device 866A detects selection of continue affordance 808B. The selectionis a user input 809B (e.g., mouse click) on continue affordance 808B. Asshown in FIG. 8AE, in response to user input 809B, device 866A displayskey confirmation interface 812B.

Key confirmation interface 812B is used to confirm correct entry of theaccess key in key field 806B (FIG. 8AE). Key confirmation interface 812Bincludes key 814B, which is representation of the key entered in keyfield 806B. Key confirmation interface 812B further includes continueaffordance 816B. While displaying key confirmation interface 812B,device 866A detects selection of continue affordance 816B. The selectionis a user input 817B (e.g., mouse click) on continue affordance 816B. Asshown in FIG. 8AF, in response to user input 817B, device 866A displaysupload interface 818B.

Upload interface 818B includes select file affordance 820B and uploadaffordance 820B. In response to a selection of select file affordance820B, device 866A provides a process by which a document (e.g., document822B) is selected for inclusion in the access request. In FIG. 8AF, theprocess initiated by selection of select file affordance 820B hasalready been used to select document 854A. In the embodiment of FIGS.8S-8AG, the document indicates a status of the user of the user account.While displaying upload interface 818B, device 866A detects selection ofthe continue affordance 824B. The selection is a user input 825B (e.g.,mouse click) on the continue affordance 898A. As shown in FIG. 8AG, inresponse to user input 825B, device 866A submits the document to aremote access service and displays confirmation interface 830B,indicating that the request for access has been submitted. In someembodiments, the request includes submitting, to a remote accessservice, the access key of FIG. 8AE as well as document 822B.

As described, an access request is provided by a beneficiary to requestaccess to the user account following a change in status of the userassociated with the user account. In some embodiments, an access requestis provided (e.g., submitted) to a remote access service, which reviewsthe document and access key provided in the access request, anddetermines if the access request is valid. In some embodiments, accessto the user account is approved if a set of beneficiary access criteriais met. As an example, the set of beneficiary access criteria caninclude a criterion that is met when the user account has been inactivefor a predetermined amount of time. As another example, the set ofbeneficiary access criteria can include a criterion that is met when thechange in status of the account has been confirmed by the remote accessservice using an independent source (e.g., obituary).

If an access request is not approved (e.g., the set of beneficiaryaccess criteria is not met), a beneficiary is notified that the accessrequest is not approved (e.g., denied), as shown in FIG. 8AH. In FIG.8AH, device 866 displays denial interface 840B, which can be a userinterface of a web browser. Denial interface 840B includes information842B, which indicates that an access request is denied because the setof beneficiary access criteria is not met. As illustrated, the set ofbeneficiary access criteria is not met at least because the user accountis still in use.

As described in FIGS. 8AI-8AM, if an access request is approved (e.g.,the set of beneficiary access criteria is met), a beneficiary isnotified that the access request has been approved, and optionally,device 866A performs a beneficiary account setup process.

In FIG. 8AI, device 866 displays approval interface 844B, which can be auser interface of a web browser. Approval interface 844B includesinformation 846B and setup affordance 848B. Information 846B indicatesthat the request to access the user account (e.g., of Jane Appleseed)has been approved and that access to the user account is available for aparticular amount of time (e.g., 6 months, 1 year).

While displaying approval interface 844B, device 866A detects selectionof the setup affordance 848B. The selection is a user input 850B (e.g.,mouse click) on the continue affordance 848B. As shown in FIG. 8AJ, inresponse to user input 850B, device 866A displays password generationinterface 852B. In some embodiments, displaying password generationinterface 852B includes overlaying password generation interface 852B onapproval interface 844B.

Password generation interface 852B includes identifier 854B and createpassword affordance 856B. Identifier 854B is a credential (e.g.,username) that can be used to access the user account. In someembodiments, the identifier 854B is provided (e.g., generated) by theremote access service, for instance, in response to approving an accessrequest. In response to selection of create password affordance 856B(e.g., user input 858B), device 866A provides a field (not shown) thatis used for entry of a passcode (e.g., a password to be used incombination with identifier 854B). Once the passcode has been entered,device 866A displays multi-factor interface 860B, as shown in FIG. 8AK.In some embodiments, displaying multi-factor interface 860B includesoverlaying multi-factor interface 860B on approval interface 844B.

Multi-factor interface 860B includes contact information field 862B andcontinue affordance 864B. In some embodiments, multi-factor interface860B is displayed with contact information field 862B unpopulated.Contact information field 862B is used to enter a set of contactinformation (e.g., phone number, email address) that can be used toimplement multi-factor authentication. In this manner, multi-factorauthentication may be implemented for access to the user account. Whiledisplaying multi-factor interface 860B with contact information field862B populated, device 866A detects selection of continue affordance864B. The selection is a user input 866B (e.g., mouse click) on thecontinue affordance 864B. As shown in FIG. 8AL, in response to userinput 866B, device 866A displays contact information interface 868B. Insome embodiments, displaying contact information interface 868B includesoverlaying contact information interface 868B on approval interface844B.

Contact information interface 868B includes contact information field870B and continue affordance 872B. In some embodiments, contactinformation interface 868B is displayed with contact information field870B unpopulated Contact information field 870B is used to enter a setof contact information (e.g., phone number, email address) for thebeneficiary. While displaying contact information interface 868B, device866A detects selection of the continue affordance 872B with contactinformation field 870B populated. The selection is a user input 874B(e.g., mouse click) on the continue affordance 874B. As shown in FIG.8AM, in response to user input 874B, device 866A displays completioninterface 876B, indicating that the beneficiary setup process iscomplete. In some embodiments, displaying completion informationinterface 868B includes overlaying contact information interface 868B onapproval interface 844B.

After completing the beneficiary setup process, the user account for(e.g., the user account for Jane Appleseed) can be accessed using theset of beneficiary credentials of FIGS. 8AJ-8AL. In FIG. 8AN, device866A displays an account management interface 880B for the user account.Account management interface 880B includes account features 882B, whichcan be used to manage various aspects of the user account. As anexample, account feature 882Ba can be used to access data of the useraccount (e.g., photos, videos, calendar, contacts).

In some embodiments, a beneficiary can access a device backup associatedwith the user account. In some embodiments, the device backup does notinclude data that was only locally stored on a device associated withthe user account being accessed, because such data was not included inan online backup. In some embodiments, the device backup provides accessonly to particular types of data (e.g. photos, contacts, calendar, cloudstorage).

In FIG. 8AO, device 883B is operating in a factory reset state (e.g.,includes no personalized data for a user account) and displays initialinterface 884B. In some embodiments, device 883B includes one or morefeatures of devices 100, 300, and/or 500. Initial interface 884Bincludes setup affordance 886B. While displaying initial interface 884B,device 883B detects selection of the setup affordance 886B. Theselection is a tap gesture 888B on setup affordance 886B. As shown inFIG. 8AP, in response to user input 888B, device 883B displays logininterface 890B.

Login interface 890B includes identifier field 892B, password field894B, and continue affordance 896B. In some embodiments, login interface980B is initially displayed with fields 892B and 894B unpopulated.Fields 892B, 894B are used for entry of the set of beneficiarycredentials (e.g., beneficiary username and password for the useraccount). While displaying login interface 809B with fields 892B and894B populated, device 883B detects selection of the continue affordance896B. The selection is a tap gesture 898B on continue affordance 896B.In response to user input 898B, device 833B determines if the set ofbeneficiary credentials is valid for the user account. If so, device833B displays authentication interface 802C. In some embodiments, if thecredentials are not valid, authentication interface 802C is notdisplayed and/or device 883B requests valid credentials.

Authentication interface 802C includes code field 804C, which is usedfor entry of a passcode provided to the beneficiary. In some examples,the passcode is provided to a device (e.g., device 890) associated withthe beneficiary. Authentication interface 802C further includes continueaffordance 806C. While displaying authentication interface 802C withcode field 804C populated, device 883B detects selection of the continueaffordance 806C. The selection is a tap gesture 808C on continueaffordance 806C. In response to user input 808C, device 883B displaysaccess code interface 810C, as shown in FIG. 8AR.

Access code interface 810C includes camera preview 812C and manual entryaffordance 814C. Access code interface 810C is used for entry of anaccess key for the user account. Accordingly, live preview 810C showsthe output of a camera of device 833B such that device 833B can be usedto scan a QR code including the access key for the user account (e.g.,QR code 806 of FIG. 8P). In response to selection of manual entryaffordance 814C, device 833B displays an interface that is used tomanually enter an alphanumeric representation of the access key (e.g.,alphanumeric code 808A of FIG. 8P).

After receiving an entry of the access key, device 833B determineswhether the access key is valid. If so, device 833B loads a devicebackup associated with the user account, as shown in FIG. 8AS, providingthe beneficiary (e.g., John Appleseed) with access to the device backupassociated with the user account (e.g., Jane Appleseed's user account).In some embodiments, if the access code is not valid, device 833B doesnot load the device backup and/or requests a valid access key.

FIG. 9 is a flow diagram illustrating a method for obtaining accountaccess using a computer system in accordance with some embodiments.Method 900 is performed at a computer system (e.g., 100, 300, 500, 600)(e.g., a personal computer, a tablet, a smartphone) that is incommunication with one or more input devices (e.g., a touch-sensitivesurface, a mouse, a keyboard). Some operations in method 900 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way for obtainingaccount access. The method reduces the cognitive burden on a user forobtaining account access, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to recover account access faster and more efficientlyconserves power and increases the time between battery charges.

The computer system (e.g., 600) receives (902), via the one or moreinput devices, a request (e.g., 858A, 825B) to initiate a process toaccess an account (e.g., a data account, an account that is associatedwith data of a user, including email, text messages, and media; asecured account that requires authentication to access) of an individual(e.g., a user).

The process to access the account of the individual includes providingan authentication code (e.g., 806A, 808A, 814B) to another device (e.g.,access key, QR code). In some embodiments, the authentication codeincludes a first key for account access and a second key for access todata associated with the account. In some embodiments, the code includesa key (e.g., decryption key). In some embodiments, the another device isa remote device (e.g., server). In some embodiments, the code isprovided as an image. In some embodiments, the code is provided as analphanumeric string. In some embodiments, the authentication code isstored on the computer system, and the computer system automaticallyprovides the authentication code in response to the request to initiatethe process to access the account of the individual. In someembodiments, the authentication code is manually entered (e.g.,identified) by a user, for instance, using a file browser or keyboard.In some embodiments, the authentication code is different from theauthentication credentials that would be normally used to access theaccount (e.g., is different than the account password).

The process to access the account of the individual includes providing adocument (e.g., 854A, 822B) indicative of a status of the individual tothe another device. In some embodiments, the document is a deathcertificate for the user. In some embodiments, the document is a PDF oran image, though it will be appreciated that the document may be anelectronic document of any known type. In some embodiments, once thecode and document have been provided, the computer system confirms thatthe request to access the account has been submitted).

In accordance with a determination that a set of validation criteria issatisfied, the computer system receives (904) a credential (e.g., 854B)to access the account of the individual (e.g., receiving a user nameassociated with the account that is specific to the user requestingaccess. In some embodiments, the user is further prompted to create apassword for future authentication). The set of validation criteriaincludes a first criterion that is satisfied when the authenticationcode (e.g., 806A, 808A, 814B) is valid and a second criterion that issatisfied when the document (e.g., 854A, 822B) is valid. In someembodiments, the authentication code is validated by one or more remotedevices. In some embodiments, after providing the document, the veracityof the document (e.g., 854A, 822B) is automatically and/or manuallyverified, for instance, by a third-party. In some embodiments, inaccordance with a determination that the set of validation criteria arenot satisfied, the computer system does not receive (e.g., forgoesreceiving) a credential to access the account of the individual.Providing credential for accessing an account in response to validationcriteria being satisfied provides a manner in which a user (e.g.,beneficiary) can quickly and efficiently recover access to a device ofan individual, for instance, if the account beneficiary would otherwisebe unable to access the device, which reduces the number of inputsneeded to perform an operation.

In some embodiments, the computer system is associated with an account(e.g., account for John Appleseed) of a first user (e.g., 832 a, 852 a)of the computer system. In some embodiments, the computer systemperforms an account beneficiary (e.g., trustee) selection process. Insome embodiments, the account beneficiary selection process includesreceiving a first set of one or more user inputs that includes a firstinput (e.g., 838, 856) corresponding to a first contact (e.g., 832 a,852 a) (e.g., a contactable user with contact information; a contactableuser account) associated with the account of the first user (e.g., aninput on an affordance corresponding to the contact). In someembodiments, the account beneficiary selection process includes, inresponse to receiving the first set of one or more user inputs,providing, to the first contact, a notification (e.g., 872, 874) (e.g.,indicating that the contact has been selected as a beneficiary for anaccount of the user) that indicates that the first contact has beenrequested (e.g., a request that does not need approval/acceptance) as abeneficiary of the account of the first user (e.g., an individual who isauthorized to request access to the account of the first user undercertain circumstances (e.g., process 900). In some embodiments, thenotification is provided using a messaging application. In someembodiments, the notification, when selected by the contact, causesdisplay of a beneficiary notification interface on a device of thecontact.

In some embodiments, in response to receiving the first set of one ormore user inputs (e.g., 838, 846, 856, 858, 866, 880, 886, 800A), and inaccordance with a determination that the first contact is a contact of afirst type (e.g., if a device of the contact satisfies a set ofcompatibility criteria (e.g., belongs to a same device ecosystem) as thecomputer system), the computer system causes (e.g., automaticallyadding; adding without requiring approval/acceptance) the contact (e.g.,832 a, 852 a) to be added as a beneficiary of the account of the firstuser. In some embodiments, adding the contact as a beneficiary for theaccount of the user includes providing the authentication code to theselected contact without receiving additional user input. In someembodiments, the authentication code is provided with the notification.In some embodiments, adding the beneficiary includes adding thebeneficiary to a list of beneficiaries for the user account. In someembodiments, a beneficiary may be removed from the user account. In someembodiments, removing the beneficiary invalidates the authenticationcode. Causing contacts to be added as beneficiaries in response todetermining the contacts are a particular type allows a user to quicklyand efficiently add contacts as account beneficiaries for their account,which reduces the number of inputs needed to perform an operation.

In some embodiments, in accordance with a determination that the contactis not a contact of the first type (e.g., if the device of the contactdoes not a set of compatibility criteria), the notification includes animage (e.g., 804A) of a second authentication code for use in a processto access the account of the user. In some embodiments, a contact not ofthe first type is not automatically added as an account beneficiary. Insome embodiments, the individual may instead elect to send theauthentication code using other means. In some embodiments, theauthentication code is sent as an image to the contact, for instance,using a messaging application. In some embodiments, the authenticationcode can be printed and provided to the selected contact by other means(e.g., offline) (e.g., without adding the contact as a beneficiary inresponse to (e.g., automatically in response to) the first user input).In some embodiments, contacts not of the first type are automaticallyadded as beneficiaries and removal of a beneficiary invalidates theauthentication code.

In some embodiments, performing the account beneficiary selectionprocess further includes displaying an account beneficiary selectioninterface (e.g., 830) that includes a plurality of candidate accountbeneficiary contact user-interactive graphical objects (e.g., 832 a-c).In some embodiments, the plurality of candidate account beneficiarycontact user-interactive graphical objects includes a first candidateaccount beneficiary contact user-interactive graphical object (e.g., 832a) that corresponds to the first contact that meets one or more trustcriteria. In some embodiments, the plurality of candidate accountbeneficiary contact user-interactive graphical objects includes a secondcandidate account beneficiary contact user-interactive graphical object(e.g., 832 b) that corresponds to a second contact that meets one ormore trust criteria, different from the first contact. In someembodiments, the first input of the set of one or more user inputs is aninput (e.g., 838) corresponding to the first candidate accountbeneficiary contact user-interactive graphical object. In someembodiments, in response to selection of the contact selectionaffordance, the computer system displays a contact interface (e.g., listof device contacts, list of account contacts) including contacts of thefirst type and contacts of the second type.

In some embodiments, providing the authentication code (e.g., 806A,808A, 814B) includes providing the authentication code in response tothe request (e.g., 858A, 825B) to initiate the process to access theaccount of the individual (e.g., automatically in response to; withoutrequiring further input other than the request to initiate). In someembodiments, the authentication code is provided upon initiation of theaccount access process. In some embodiments, the authentication code isprovided in this manner when a computer system (e.g., device) of theaccount beneficiary shares a device ecosystem with the computer systemof the individual of the account. Providing the authentication code inresponse to the request to initiate the process to access the account ofthe individual allows for the authentication code to be provided withoutrequiring additional user input, which reduces the number of inputsneeded to perform an operation.

In some embodiments, providing the authentication code includesdisplaying an authentication code entry user-interactive graphicalobject (e.g., 806B) (e.g., a text box). In some embodiments, providingthe authentication code includes receiving, via the one or more inputdevices, a set of one or more user inputs that includes entry of theauthentication code (e.g., receive manual entry of the authenticationcode) in the authentication code entry user-interactive graphicalobject. In some embodiments, the authentication code is providedmanually prior to submitting a request to access the account of theindividual. In some embodiments, the authentication code is providedmanually, for instance, using a web interface, when a computer system(e.g., device) of the account beneficiary does not share a deviceecosystem with the computer system of the individual of the account.

In some embodiments, the process to access the account of the individualincludes providing a set of personal information (e.g., 882A) (e.g.,personal identification information, address, email, date of birth) forthe individual of the account. In some embodiments, the computer systemprovides personal information for the individual of the account and/orthe account beneficiary.

In some embodiments, after providing the document indicative of thestatus of the individual, the computer system receives a notification(e.g., 842B, 846B) indicating whether access to the account of theindividual has been approved. In some embodiments, the notification is anotification received at a device and the notification is provided by asystem level function (e.g., operating system notification). In someembodiments, of the request has been approved, selection of thenotification initiates a beneficiary set up process for creating a loginto the account of the individual. In some embodiments, the notificationis an e-mail. In some embodiments, if the request has been approved, thee-mail optionally includes an account setup affordance. In someembodiments, the account setup affordance includes a hyperlink to aportal for performing the beneficiary set up process. In someembodiments, a request is denied for instance, due to ongoing activityof the account of the individual.

In some embodiments, the notification includes an indication (e.g.,846B) that access to the account of the individual has been approved. Insome embodiments, the notification includes an account setupuser-interactive graphical object (e.g., 848B) (e.g., an affordance). Insome embodiments, the computer system detects selection (e.g., 850B) ofthe account setup user-interactive graphical object. In someembodiments, in response to detecting selection of the account setupuser-interactive graphical object, the computer system initiates abeneficiary account setup process. In some embodiments, the beneficiaryset up process is a process by which a beneficiary registers an accountwith a service to generate a set of beneficiary credentials foraccessing the account of the individual. In some embodiments, the set ofbeneficiary credentials may be used to access the account of theindividual of (e.g., account management features) and/or data associatedwith the account of the individual (e.g., photos, applications,contacts. In some embodiments, during the beneficiary set up process,the beneficiary provides a set of personal information for thebeneficiary (e.g., personal identification information, address, phonenumber email, date of birth). Detecting selection of an account setupuser-interactive graphical object and initiating a beneficiary set upprocess in response to selection of the account setup affordance allowsfor a beneficiary set up process to be quickly and efficientlyinitiated, which reduces the number of inputs needed to perform anoperation.

In some embodiments, the beneficiary account setup process includesproviding a set of personal information (e.g., information entered intofields 888A) (e.g., personal identification information, address, phonenumber email, date of birth) for an account beneficiary of the accountof the individual. In some embodiments, personal information isconfirmed and/or newly entered. In some embodiments, the beneficiaryaccount setup process includes providing a set of beneficiarycredentials (e.g., 854B, password entered in response to input 858B)including the credential (e.g., 854B) for the account beneficiary toaccess the account of the individual. In some embodiments, thebeneficiary provides credentials, such as a password, that will be usedin a set of beneficiary credentials for accessing the account of theindividual. In some embodiments, the set of beneficiary credentials(e.g., 854B, password created using affordance 856B, credentials enteredin fields 892B, 894B) are used to access one or more secured functions(e.g., accessing device backup of device 883B (FIG. 8AS)) of the accountof the individual. In some embodiments, the beneficiary credentialsinclude a user name and a password. In some embodiments, the user nameis provided by the account recovery service and the password is providedby the beneficiary during the beneficiary set up process. In someembodiments, in response to submitting the beneficiary credentialsduring an access, the beneficiary is prompted to provide an access code.In some embodiments, the access code is a two-factor authentication codeprovided to the beneficiary's account and/or device (e.g., a deviceseparate from the computer system displaying the login interface). Insome embodiments, the access code (e.g., QR code, decryption key) is anauthentication code for the account of the individual. In someembodiments, access requires both the two-factor authentication code andauthentication code for the account of the individual. In someembodiments, access is provided to all secured functions of an account.In some embodiments, access is provided to a subset of all securedfunctions of an account. In some embodiments, access is provided onlyfor secured functions provided on a device configured for thebeneficiary. In some embodiments, access is provided for data for theaccount (e.g., photos, contacts, calendar)). In some embodiments,web-based access is not provided to a beneficiary such that data for theaccount cannot be accessed using a web browser.

FIGS. 10A-10Z illustrate exemplary user interfaces for disabling anaccount recovery service, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 11 .

Generally, various techniques for disabling an account recovery servicedescribed below allow a user to disable an account recovery serviceassociated with their user account. In some embodiment, such techniquesensure an alternative account recovery function is enabled for the useraccount prior to disabling the account recovery service, therebyensuring a user can recover their account after disabling the accountrecovery service.

FIGS. 10A-10E illustrate techniques for attempting to disable an accountrecovery service for a user account in which an alternative accountrecovery function is not enabled. In some embodiments, an alternativeaccount recovery function is any function and/or feature by which a usercan recover their account, including but not limited to a recoverycontact and/or a recovery key.

FIG. 10A illustrates electronic device 600. In FIG. 10A, electronicdevice 600 is a portable multifunction device and has one or morecomponents described above in relation to one or more of devices 100,300, and 500.

In FIG. 10A, device 600 displays, on display 602, an account interface1004 for a user account of a user Jane Appleseed. The account interface1004 is associated with a user account of device 600 in someembodiments. The account interface 1004 includes various affordances forconfiguring features of the user account, including security affordance1006. In response to selection of security affordance 1006, device 600displays a security interface. For example, while displaying accountinterface 1004, device 600 detects selection of security affordance1006. The selection is a tap gesture 1008 on security affordance 1006.As shown in FIG. 10B, in response to detecting tap gesture 1008, device600 displays security interface 1010.

Security interface 1010 includes various affordances for managing accessto the user account and/or data associated with the user account,including account recovery affordance 1012. In response to selection ofaccount recovery affordance 1012, device 600 displays an accountrecovery interface. For example, while displaying security interface1010, device 600 detects selection of account recovery affordance 1012.The selection is a tap gesture 1014 on account recovery affordance 1012.As shown in FIG. 10C, in response to detecting tap gesture 1014, device600 displays account recovery interface 1016.

Account recovery interface 1016 includes recovery service affordance1018 and add recovery function affordance 1092. Selection of addrecovery function affordance 1092 causes device 600 to initiate aprocess for adding an account recovery function, such as a recoverycontact or an account recovery service, for a user account (e.g., JaneAppleseed's account) (e.g., as described with respect to process 600).In response to selection of recovery service affordance 1018, device 600displays a recovery service interface. For example, while displayingaccount recovery interface 1016, device 600 detects selection ofrecovery service affordance 1018. The selection is a tap gesture 1020 onrecovery service affordance 1018. As shown in FIG. 10D, in response todetecting tap gesture 1020, device 600 displays recovery serviceinterface 1022.

Recovery service interface 1022 includes remove service affordance 1024.In response to selection of remove service affordance 1024, via tapgesture 1026, device 600 initiates a process for disabling the accountrecovery service for the user account. In some embodiments, the recoveryservice associated with recovery service interface 1022 is a firstparty, cloud-based recovery service provided by the manufacturer ofdevice 600 and/or the provider of the operating system of device 600(e.g., a default recovery service).

In some embodiments, the process for disabling the account recoveryservice includes determining whether a set of service removal criteriahave been met. In some embodiments, the set of service removal criteriaincludes a criterion that is met when an alternative account recoveryfunction is enabled for the user account. Such alternative accountrecovery functions include but are not limited to recovery contacts andrecovery keys.

If device 600 (or an external device in communication with device 600)determines that service removal criteria is not met, device 600 promptsa user to enable (e.g., add) an alternative account recovery functionfor their user account. For example, as illustrated in FIG. 10E, device600 determines that service removal criteria is not met (e.g., noalternative account recovery function is enabled for the user account)and displays add recovery function interface 1028 including continueaffordance 1028 a and cancel affordance 1028 b. In some embodiments, addrecovery function interface 1028 is overlaid on recovery assistanceinterface 1022.

In response to selection of continue affordance 1028 a, device 600initiates a process for adding an alternative account recovery function(e.g., recovery contact) to the user account (e.g., a process for addinga recovery contact as described with respect to FIGS. 6C-6J).Thereafter, the user, optionally, completes the process for disablingthe account recovery service, as described below. In response toselection of affordance 1028 b, device 600 ceases display of addrecovery function interface 1028 and terminates the process fordisabling the account recovery service.

FIGS. 10F-10I illustrate techniques for disabling an account recoveryservice for a user account in which an alternative account recoveryfunction is enabled.

In FIG. 10F, device 600 displays account recovery interface 1016 (e.g.,in response to selection of an account recovery affordance of a securityinterface, such as the tap gesture 1014 of FIG. 10B). Account recoveryinterface 1016 includes recovery service affordance 1018 and addrecovery function affordance 1092. As described, selection of addrecovery function affordance 1092 initiates a process for adding anaccount recovery function for a user account (e.g., Jane Appleseed'saccount) (e.g., as described with respect to process 600). Because analternative account recovery function (e.g., recovery contact JohnAppleseed) is enabled for the user account, account recovery interface1016 further includes recovery contact affordance 1030 corresponding toa recovery contact of the user account.

While displaying account recovery interface 1016, device 600 detectsselection of recovery service affordance 1018. The selection is a tapgesture 1032 on recovery service affordance 1018. As shown in FIG. 10G,in response to detecting tap gesture 1032, device 600 displays recoveryservice interface 1022.

Recovery service interface 1022 includes recovery service removalaffordance 1024. In response to selection of remove service affordance1024, device 600 initiates a process for disabling the account recoveryservice for the user account.

As described, the process for disabling the account recovery serviceincludes determining whether a set of service removal criteria have beenmet. If device 600 (or an external device in communication with device600) determines that the set of service removal criteria have been met,device 600 disables the account recovery service for the user account.In response to selection of remove service affordance 1024, device 600displays a completion interface. For example, while displaying recoveryservice interface 1022, device 600 detects selection of remove serviceaffordance 1024. The selection is a tap gesture 1034 on remove serviceaffordance 1024. As shown in FIG. 10H, in response to selection ofremove service affordance 1024, device 600 displays completion interface1036. In some embodiments, one or more confirmation notifications and/orinterfaces (e.g., notifications and/or interfaces requiring additionalconfirmation inputs) are shown prior to completing the removal anddisplay of completion interface 1036.

Completion interface 1036 includes information 1037 and completionaffordance 1038. Information 1037 indicates that the process to disablethe account recovery service for the user account has been completed,and optionally, that account recovery for the user account requires useof an alternative account recovery function. In response to selection ofcompletion affordance 1038, device 600 displays (e.g., resumes displayof) account recovery interface 1016, as shown in FIG. 10I. Because theaccount recovery service has been disabled for the user account,recovery service affordance 1018 (FIG. 6F) is no longer included inaccount recovery interface 1016.

In some embodiments, prior to completing the process to disable anaccount recovery service, device 600 requires that a user confirms oneor more aspects of an alternative account recovery function. Forexample, as shown in FIG. 10J, device 600 displays confirmationinterface 1042 (e.g., after receiving tap gesture 1034 and prior todisplaying completion interface 1036). In some embodiments, confirmationinterface 1042 is displayed (e.g., overlaid on recovery serviceinterface 1022) in response to selection of a remove service affordance,such as remove service affordance 1024 (FIG. 10G). Confirmationinterface 1042 includes continue affordance 1042 a and cancel affordance1042 b. In response to selection of cancel affordance 1042 b, devices600 terminates the process for disabling the account recovery service.

In response to selection of continue affordance 1042 a, device 600initiates a process for confirming information associated with arecovery contact to the user account. In response to selection ofcontinue affordance 1042 a, device 600 displays a recovery contactconfirmation interface. For example, while displaying confirmationinterface 1042, device 600 detects selection of continue affordance 1042a. The selection is a tap gesture 1044 on continue affordance 1042 a. Asshown in FIG. 10K, in response to detecting tap gesture 1044, device 600displays recovery contact confirmation interface 1050.

Recovery contact confirmation interface 1050 includes recovery contactaffordance 1052 and continue affordance 1054. Selection of recoverycontact affordance 1052 allows for a user to confirm and/or update oneor more aspects of a recovery contact corresponding to recovery contactaffordance 1052 (e.g., John Appleseed). For example, selection ofrecovery contact affordance 1052 causes, in some embodiments, device 600to display one or more interfaces through which a user can specifyinformation associated with the recovery contact. In response toselection of continue affordance 1054, device 600 completes the processfor disabling the account recovery service and displays a completioninterface, such as completion interface 1036 (FIG. 10H), indicating thatthe process for disabling the account recovery service has beencompleted.

While description is made herein with respect to device 600 providingfor a user to confirm details associated with a recovery contact it willbe appreciated that, in some embodiments, device 600 additionally oralternatively confirms (or initiates a process to confirm via anexternal device) information about one or more other alternative accountrecovery functions, such as an additional recovery contact and/or arecovery key (e.g., confirming that a user is in possession of arecovery key prior to removal of the account recovery service).Thereafter, the user, optionally, completes the process for disablingthe account recovery service, as described.

In some embodiments, after initiating the process to disable the accountrecovery service (e.g., in response to selection of recovery serviceremoval affordance 1024 (FIG. 10D), device 600 determines whether apasscode is enabled on device 600. If so, device 600 continues toperform the process to disable the account recovery service, asdescribed. If not, device 600 prompts a user to provide a passcode fordevice 600. For example, as shown in FIG. 10L, if device 600 determinesthat no passcode is enabled on device 600, device 600 displays passcodeinterface 1056. In some embodiments, passcode interface 1056 is overlaidon recovery service interface 1022.

Passcode interface 1056 includes continue affordance 1056 a and cancelaffordance 1056 b. In response to selection of cancel affordance 1056 b,devices 600 terminates the process for disabling the account recoveryservice. In response to selection of continue affordance 1056 a, device600 provides (e.g., displays) a passcode entry interface for providing apasscode. For example, while displaying confirmation interface 1056,device 600 detects selection of continue affordance 1056 a. Theselection is a tap gesture 1058 on continue affordance 1056 a. As shownin FIG. 10M, in response to detecting tap gesture 1058, device 600displays passcode entry interface 1060.

Passcode entry interface 1060 includes passcode progress indicator 1062and continue affordance 1064. Passcode progress indicator 1062 indicatesthe number of passcode digit entries a user has made while entering thepasscode, for instance, using the numeric keypad of the passcode entryinterface 1060. In some embodiments, passcode progress indicator 1062displays the numbers selected for the passcode. In other embodiments,passcode progress indicator 1062 does not display the numbers selectedfor the passcode (e.g., the selected numbers are hidden). In response toselection of continue affordance 1064, device 600, optionally, confirmsthe passcode is valid and continues to perform the process to disablethe account recovery service, as described.

In some embodiments, after (e.g., upon) initiating the process todisable the account recovery service (e.g., in response to selection ofrecovery service removal affordance 1024 (FIG. 10D), device 600determines whether software (e.g., an operating system) of device 600and/or one or more external devices satisfies version criteria. In someembodiments, version criteria is satisfied when a version of software isa particular version (e.g., latest version) of the software.

If device 600 determines that version criteria is met, device 600continues to perform the process to disable the account recoveryservice, as described. If not, device 600 terminates the process todisable the account recovery service and provides an indication as towhich of device 600 and the one or more external devices includesoftware that does not satisfy the version criteria. For example, asshown in FIG. 10N, if device 600 determines that version criteria is notmet, device 600 displays device interface 1070. In some embodiments,device interface 1070 is overlaid on recovery service interface 1022.

Device interface 1070 includes device list affordance 1070 a and cancelaffordance 1070 b. In response to selection of cancel affordance 1056 b,device 600 ceases to display device interface 1070. In response toselection of device list affordance 1070 a, device 600 provides (e.g.,displays) a device update interface indicating which of the devicesinclude software that failed the version criteria. For example, whiledisplaying device interface 1070, device 600 detects selection of devicelist affordance 1070 a. The selection is a tap gesture 1072 on continueaffordance 1070 a. As shown in FIG. 10O, in response to detecting tapgesture 1072, device 600 displays device update interface 1074. Asillustrated, device update interface 1074 includes a list of devices1075 and indicates whether each device 1075 has software that satisfiesversion criteria (e.g., has software that is up-to-date). Thereafter, auser may update software such that all devices have software thatsatisfies the version criteria and disable the account recovery serviceby reinitiating the process to disable the account recovery service.

In some instances, a user may wish to remove a recovery contact from auser account for which the account recovery service is disabled. Inresponse, device 600 prompts the user to add an alternative accountrecovery function (e.g., recovery contact) prior to removing therecovery contact. In this manner, device 600 ensures that at least onerecovery function is available for the user account after the recoverycontact is removed.

For example, in FIG. 10P, device 600 displays recovery contact interface1076. Recovery contact interface 1076 includes remove affordance 1082.In response to selection of remove affordance 1082, device 600 initiatesa process for removing the recovery contact. In some embodiments, theprocess for removing the recovery contact includes determining whetheranother alternative account recovery function is enabled for the useraccount. If so, the recovery contact is removed from the user account asa recovery contact. If not, device 600 prompts a user to add analternative account recovery function to their user account. Forexample, while displaying confirmation interface 1076, device 600detects selection of remove affordance 1082. The selection is a tapgesture 1084 on remove affordance 1082. As shown in FIG. 10Q, inresponse to detecting tap gesture 1084, device 600 displays add recoveryfunction interface 1082. In some embodiments, add recovery functioninterface 1082 is overlaid on confirmation interface 1076.

Add recovery function interface 1082 includes add recovery functioninterface continue affordance 1082 a and cancel affordance 1082 b. Inresponse to selection of cancel affordance 1082 a, device 600 terminatesthe process for removing the recovery contact. In response to selectionof continue affordance 1082 b, device 600 initiates a process for addingan alternative account recovery function (e.g., recovery contact) to theuser account.

FIGS. 10R-10S illustrate exemplary recovery contact notifications. Insome embodiments, device 600 notifies a user if a recovery contact failsto satisfy recovery contact criteria. In some embodiments, recoverycontact criteria includes a criterion that is satisfied if a recoverycontact has not removed themselves as a recovery contact. Accordingly,if a recovery contact removes themselves as a recovery contact, device600 displays a notification, such as the notification 1088 of FIG. 10R,indicating that recovery contact has removed themselves as a recoverycontact and that the user should update and/or enable one or morealternative account recovery functions for the user account of the user.

In some embodiments, recovery contact criteria includes a criterion thatis satisfied if a recovery contact has been active within a thresholdamount of time. Accordingly, if a recovery contact is inactive for atleast the threshold amount of time (e.g., a week, two weeks, a month, 6months), device 600 displays a notification, such as the notification1090 of FIG. 10S, indicating that the recovery contact has been inactivefor the threshold amount of time and that the user should update and/oradd one or more alternative account recovery functions.

FIGS. 10T-10W illustrate techniques for enabling an account recoveryservice for a user account. In FIG. 10T, device 600 displays the accountrecovery interface 1016 including an add recovery function affordance1092.

As described, selection of recovery function affordance 1092 initiates aprocess for adding an account recovery function. For example, whiledisplaying account recovery interface 1016, device 600 detects selectionof add recovery function affordance 1092. The selection is a tap gesture1094 on add recovery function affordance 1092. As shown in FIG. 10U, inresponse to detecting tap gesture 1094, device 600 displays add accountrecovery function interface 1096.

Add account recovery function interface 1096 includes add recoverycontact affordance 1098 and add account recovery service affordance1000A. In response to selection of the add recovery contact affordance1098, device 600 initiates a process to add a recovery contact to theuser account. In response to selection of the add account recoveryservice affordance 1000A, device 600 initiates a process for enablingthe account recovery service for the user account. For example, whiledisplaying add account recovery function interface 1096, device 600detects selection of add account recovery service affordance 1000A. Theselection is a tap gesture 1002A on add account recovery serviceaffordance 1000A. As shown in FIG. 10V, in response to detecting tapgesture 1002A, device 600 displays add recovery service interface 1004A.

Add recovery service interface 1004A includes add affordance 1006A. Inresponse to selection of add affordance 1006A, the account recoveryservice is enabled for the user account, and device 600 displays (e.g.,resumes display of) account recovery interface 1016, as shown in FIG.10W. Because the account recovery service has been enabled for the useraccount, the account recovery interface 1016 includes recovery serviceaffordance 1018.

While description has been made herein with respect disabling an accountrecovery service for recovery of a user account, in some examples, auser may additionally or alternatively wish to disable web access todata for the user account. In some embodiments, this includes causing aservice hosting data for the user account to delete at least a portionof the data for the user account. Data for a user account may thereafterbe stored locally on one or more user devices, such as device 600. Insome embodiments, disabling web access includes encrypting data hostedby the service such that the service can no longer read the data. FIGS.10X-10Z illustrate techniques for disabling access to data.

In FIG. 10X, device 600 displays security interface 1010 including dataaccess option 1012A. As illustrated, data access option 1012A is in anenabled state indicating that data associated with the user account canbe accessed by the service.

While displaying security interface 1010, device 600 detects selectionof data access option 1012A. The selection is a tap gesture 1014A ondata access option 1012A. As shown in FIG. 10Y, in response to selectionof option 1012A, device 600 displays data access interface 1016A.

Data access interface 1016A includes access removal affordance 1018A.While displaying data access interface 1016A, device 600 detectsselection of access removal affordance 1018A. The selection is a tapgesture 1020A on access removal affordance 1018A. As shown in FIG. 10Z,in response to selection of access removal affordance 1018A, device 600displays security interface 1010 in which data access option 1012A is ina disabled state, indicating that data associated with the user accountcannot be accessed by the service.

FIG. 11 is a flow diagram illustrating a method for disabling an accountrecovery service using a computer system in accordance with someembodiments. Method 1100 is performed at a computer system (e.g., 100,300, 500, 600) (e.g., a personal computer, a tablet, a smartphone) thatis in communication with a display generation component (602) (e.g., atelevision, a display controller, an internal or externaltouch-sensitive display system) and one or more input devices (e.g., atouch-sensitive surface, a mouse, a keyboard). Some operations in method1100 are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 1100 provides an intuitive way for disablingan account recovery service. The method reduces the cognitive burden ona user for disabling an account recovery service, thereby creating amore efficient human-machine interface. For battery-operated computingdevices, enabling a user to disable an account recovery service fasterand more efficiently conserves power and increases the time betweenbattery charges.

The computer system (e.g., 600) receives (1102), via the one or moreinput devices, a set of one or more inputs (e.g., 1026, 1034, 1040,1044, 1058) (e.g., user inputs) corresponding to a request to disable anaccount recovery service (e.g., an account recovery servicecorresponding to the recovery service affordance 1018) for a useraccount. In some embodiments, the set of one or more inputs includes atouch input (e.g., 1026, 1034, 1040, 1044, 1058). In some embodiments,the set of one or more inputs includes a speech input. In someembodiments, the account recovery service is a cloud-based service forrestoring account access (e.g., a cloud-based service that hosts one ormore aspects of a user account including authentication informationand/or data associated with the user account). In some embodiments, theservice is a first-party service (e.g., provided by a developer and/ordistributor of an operating system of the computer system). In someembodiments, the service authenticates a user during an authenticationprocess and/or stores data (e.g. photos, contacts, calendar) associatedwith the user account. In some embodiments, when disabling the accountrecovery service, the account recovery service is removed from theaccount recovery service the computer system and/or one or more devicesassociated with a user account. In some embodiments, when disabling theaccount recovery service, the account recovery service remains on thecomputer system (e.g., 600) and/or one or more devices associated withthe user account (e.g., 1075 a, 1075 b).

In response to receiving the set of one or more inputs corresponding toa request to disable the account recovery service, the computer systeminitiates (1104) a process for disabling the account recovery servicefor the user account. In some embodiments, disabling the accountrecovery service from the user account includes disabling the servicesuch that the service is no longer available to perform account recoveryusing the service.

In some embodiments, the process for disabling the account recoveryservice for the user account includes (1106), in accordance with adetermination that the user account satisfies a set of service removalcriteria, disabling (1108) the account recovery service for the useraccount. In some embodiments, the process includes determining whetherthe user account satisfies service removal criteria. In someembodiments, the service removal criteria includes a requirement thatone or more of a set of alternative account recovery functions (e.g., arecovery contact (e.g., a recovery contact corresponding to recoveryaffordance 1030) (e.g., a personal contact that is authorized to assistthe user of the account with a recovery function), recovery key) isenabled for the user account. In some embodiments, the service removalcriteria requires that a user confirm removal of the service, forinstance, using a prompt (e.g., 1042) provided (e.g., displayed) by thecomputer system. In some embodiments, the service removal criteriarequires that a user be authenticated, for instance, using biometricauthentication (e.g., facial recognition). In some embodiments, theservice removal criteria includes a requirement that a security function(e.g., passcode as seen in FIG. 10M) is enabled for the computer system.In some embodiments, the service removal criteria includes a requirementthat a version of an operating system of the computer system satisfiesversion criteria (e.g., is at least a particular version (e.g., as seenin FIGS. 10N-10O). In some embodiments, the service removal criteriaincludes a requirement that an authentication function is enabled forthe computer system and/or the user account (e.g., two-factorauthentication). In some embodiments, if the service removal criteria issatisfied, the computer system removes (e.g., disassociates) the accountrecovery service from the user account. In some embodiments, prior todisabling the account recovery service, the computer system confirms oneor more aspects of an alternative account recovery function. In someembodiments, the computer system confirms the identity and/orinformation of a recovery contact. In some embodiments, the computersystem prompts a user to confirm a recovery key. In some embodiments, asa result of disabling the account recovery service, a service associatedwith the account recovery service no longer has access to data for theuser account stored by the service. In some embodiments, disabling theaccount recovery service disables web-based access to one or more typesof data associated with the user account.

In some embodiments, the process for disabling the account recoveryservice for the user account includes, in accordance with adetermination that the user account does not satisfy the set of serviceremoval criteria, displaying (1110), via the display generationcomponent, a prompt to perform a process for enabling an accountrecovery function for the user account (e.g., 1028). In someembodiments, if the service removal criteria is not satisfied (e.g., noaccount recovery function is enabled for the user account), the computersystem prompts the user to enable an account recovery function for theuser account. In some embodiments, enabling the account recoveryfunction includes adding a recovery contact for the user account. Insome embodiments, enabling the account recovery function includesgenerating and/or displaying an account recovery key for the useraccount. Displaying a prompt to perform a process for enabling anaccount recovery function if a set of service removal criteria is notsatisfied provides a quick and efficient manner for a user to enable theaccount recovery function when disabling the account recovery service,which reduces the number of inputs needed to perform an operation.

In some embodiments, the service removal criteria includes a criterionthat is satisfied when a first alternative account recovery function(e.g., recovery contact, recovery key) is enabled for the user account(e.g., as described with reference to FIGS. 10A-10E). Requiring that afirst alternative account recovery function is enabled prior todisabling the account recovery service ensures that a user can quicklyand efficiently recover their account even after disabling the accountrecovery service, which reduces the number of inputs needed to performan operation.

In some embodiments, the account recovery service is a first-partyservice (e.g., the account recovery service is provided by amanufacturer and/or provider of the computer system and/or the operatingsystem of the computer system (e.g., as described with reference to FIG.10D).

In some embodiments, prior to receiving the set of one or more inputs(e.g., 1026, 1034, 1040, 1044, 1058), the computer system displays anaccount recovery interface (e.g., 1016) (e.g., a settings interface forconfiguring and/or managing account recovery features). In someembodiments, in accordance with a determination that an authenticationfunction of a first type (e.g., two-factor authentication) is enabled(e.g., enabled for the user account and/or for the computer system), theaccount recovery interface includes an affordance (e.g., 1024), that,when selected, initiates the process for disabling the account recoveryservice for the user account. In some embodiments, the set of one ormore inputs (e.g., 1026, 1034, 1040, 1044, 1058) includes an inputcorresponding to the affordance that, when selected, initiates a processfor disabling the account recovery service. In some embodiments, inaccordance with a determination that the authentication function of thefirst type (e.g., two-factor authentication) is not enabled, the accountrecovery interface does not include the affordance (e.g., 1024) that,when selected, initiates a process for disabling the account recoveryservice for the user account. In some embodiments, the affordance (e.g.,1024) to remove the account recovery service is only available if apredetermined authentication mechanism, such as two-factorauthentication, is enabled on the computer system. Including anaffordance that disables the account recovery service in an accountrecovery interface only if an authentication function is enabled ensuresthat a user is aware of what account recovery functions are availableand/or enabled on a device, which provides improved visual feedback.

In some embodiments, the process for disabling the account recoveryservice for the user account further includes, in accordance with adetermination that prompting criteria is met, issuing (e.g., displaying,outputting audibly) a prompt (e.g., 1042) to confirm informationcorresponding to a second alternative account recovery function (e.g.,recovery contact John Appleseed). In some embodiments, the promptingcriteria is met when the process for disabling the account recoveryservice for the user account has been initiated and an alternativeaccount recovery function is enabled for the user account. In someembodiments, the computer system prompts the user of the user account toconfirm information regarding an account recovery function (e.g.,recovery contact and/or recovery key associated with the user account).In some embodiments, the prompt is a notification (e.g., 1098) displayedon the display generation component of the computer system and,optionally, includes instructions (e.g., 1037) for recovering the useraccount using the alternative recovery function.

In some embodiments, the process for disabling the account recoveryservice for the user account further includes, in accordance with adetermination that a passcode security function is not enabled on thecomputer system, initiating a process to enable the passcode securityfunction. In some embodiments, the process for disabling the accountrecovery service includes determining whether a passcode securityfunction is not enabled on the computer system. If not, the computersystem prompts (e.g., using interface 1056) a user of the computersystem to provide a passcode for the computer system. In someembodiments, the process for disabling the account recovery serviceincludes determining whether one or more devices (e.g., the computersystem and/or one or more other devices associated with the useraccount) have a particular version of an operating system. If not, thecomputer system prompts (e.g., using interface 1072) the user to updatethe operating system on the devices that do not have the particularversion of the operating system. In some embodiments, if the computersystem determines that a device does not have the particular operatingsystem, the computer system ends the process for disabling the accountrecovery service for the user account.

In some embodiments, after disabling the account recovery service forthe user account, the computer system receives a request to enable(e.g., add) the account recovery service for the user account (e.g.,1094, 1002A, 1008A). In some embodiments, in response to the request toenable the account recovery service for the user account, the computersystem initiates a process for enabling the account recovery service forthe user account. In some embodiments, enabling the account recoveryservice for the user account includes enabling the service such that theservice is available to perform account recovery using the service. Insome embodiments, enabling the account recovery service requires that auser be authenticated, for instance, using biometric authentication(e.g., facial recognition).

In some embodiments, after disabling the account recovery service forthe user account, the computer system receives an indication (e.g.,1088, 1090) that a recovery contact associated with the user account hasfailed to satisfy recovery contact criteria. In some embodiments, if arecovery contact fails to satisfy recovery contact criteria, thecomputer system receives an indication (e.g., 1088, 1090) from anexternal device indicating the same. In some embodiments, the indicationis received from a remote server, such as a first-party remote server.In some embodiments, in response to the indication that the recoverycontact associated with the user account has failed the recovery contactcriteria, the computer system displays, via the display generationcomponent, a notification indicating that the recovery contactassociated with the user account has failed the recovery contactcriteria. In some embodiments, the computer system notifies the userthat the user's recovery contact has failed to satisfy recovery contactcriteria. In some embodiments, recovery contact criteria is notsatisfied if the recovery contact removes themselves as a recoverycontact, for instance, using their own device (e.g., resulting in device600 displaying notification 1088). In some embodiments, recovery contactcriteria is not satisfied if the recovery contact is inactive (e.g.,does not use a particular device, does not login into a correspondinguser account) for at least a threshold amount of time (e.g., resultingin device 600 displaying notification 1090). In some embodiments,selection of the notification initiates a process for selecting a newrecovery contact. In some embodiments, the notification is displayed ona lock screen (e.g., lock screen of FIGS. 6R, 6S) and/or a home screenof the computer system. In some embodiments, the notification isdisplayed in a settings interface of a settings application of thecomputer system. Displaying a notification that a recovery contact hasfailed recovery contact criteria allows a user to quickly andefficiently determine that one or more changes are necessary to maintaina current and reliable recovery contact for account recovery, whichprovides improved visual feedback.

In some embodiments, the recovery contact criteria includes a criterionthat is met when the recovery contact has not removed themselves as arecovery contact (e.g., for the user account) (e.g., as described withreference to FIG. 10R).

In some embodiments, the recovery contact criteria includes a criterionthat is met when the recovery contact has been active (e.g., active onone or more devices and/or accounts associated with the recoverycontact) within a predetermined period of time (e.g., a week, a month,two months, 6 months (e.g., as described with reference to FIG. 10S).

In some embodiments, in accordance with a determination (e.g., adetermination made after disabling the account recovery service) that aprocess to sign the user account out of the last device to which theuser account is signed in, the computer system provides a prompt to adda recovery method.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIG. 11 ) are also applicable in an analogous mannerto the methods described below. For example, method 700 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 1100. For example, adding arecovery contact, as described in method 700, could be used to add arecovery contact when disabling an account recovery service, asdescribed in method 1100. For brevity, these details are not repeatedbelow.

FIGS. 12A-12K illustrate exemplary user interfaces for managing dataaccess, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 13 .

Generally, techniques for managing data access described below enable auser to access data of their user account even when a service (e.g.,first-party service) hosting the data does not have access to the data(e.g., the data is encrypted such that the service cannot read the data,as described above with respect to FIGS. 10X-10Z). As will be describedin more detail below, in some embodiments, the user accesses the data bytemporarily authorizing the service to access the data such that theuser can in turn access the data via the service.

FIGS. 12A-12F illustrate techniques for providing access to data of auser account in which access to the data by the service hosting the datahas been disabled. FIG. 12A illustrates electronic devices 603, 605. InFIG. 12A, each of electronic devices 603, 605 is a multifunction device(e.g., portable multifunction device) and has one or more componentsdescribed above in relation to one or more of devices 100, 300, 500,and/or 600. In some embodiments, devices 603, 605 are in communicationwith each other and/or one or more external devices, such as a remoteserver of a service.

In FIG. 12A, device 603 displays, on display 609, login interface 1208,which can be a user interface of a web browser in some embodiments.Login interface 1208 includes username field 1210, password field 1212,and submit affordance 1214. Username field 1210 and password field 1212are used to provide respective user account credentials to initiate aprocess to authenticate a user of device 603 in response to selection ofsubmit affordance 1214.

For example, while displaying login interface 1208, device 603 receivescredentials for a user Jane Appleseed in username field 1210 andpassword field 1212, respectively, and detects selection of the submitaffordance 1214. The selection is a user input 1216 (e.g., mouse click)on the submit affordance 1214. In response to user input 1216, device603 initiates, using the credentials, authentication of a user with aservice (e.g., first-party service) hosting data for a user account ofthe user. In some embodiments, authentication with the service requirestwo-factor authentication. Accordingly, as shown in FIG. 12B, aftersubmitting the credentials, device 603 displays authentication interface1218, prompting the user to perform two-factor authentication usingdevices 603, 605.

Authentication interface 1218 includes passcode indicator 1220, in whichthe user can enter a passcode provided to device 605 by the service(e.g., provided in notification 1222). Once the passcode has beenentered such that two-factor authentication is complete, the user isauthenticated and device 603 displays a user account interface 1223, asshown in FIG. 12C.

Because data access has been disabled for the service, user accountinterface 1223 includes information 1124 indicating that the servicecannot access data for the user account. User account interface 1223further includes access affordance 1225, which when selected, initiatesa process for enabling (e.g., temporarily enabling) data access by theservice such that the user can access the data using device 603 (ordevice 605).

For example, while displaying user account interface 1223, device 603detects selection of access affordance 1225. The selection is a userinput 1226 (e.g., mouse click) on access affordance 1225. As shown inFIG. 12D, in response to selection of access affordance 1225, device 603displays confirmation interface 1227 and device 605 displaysnotification 1230 on lock screen interface 629. Confirmation interface1227 includes acknowledgement affordance 1228, which when selected,causes device 603 to display a data interface, described in furtherdetail below.

In response to selection of notification 1230, device 605 prompts a userto authorize the service to access data associated with the useraccount. For example, while displaying notification 1230 on lock screeninterface 1229, device 604 detects selection of notification 1230. Theselection is a tap gesture 1232 on notification 1230. As shown in FIG.12E, in response to detecting tap gesture 1232, device 605 displaysaccess authorization interface 1233.

Access authorization interface 1233 includes access rejection affordance1234 and access approval affordance 1236. Selection of access rejectionaffordance 1234 causes device 605 to terminate the process forauthorizing the service to access data. Selection of access approvalaffordance 1236 causes device 605 to display an access confirmationinterface. For example, while displaying access authorization interface1233, device 605 detects selection of access approval affordance 1236.The selection is a tap gesture 1238 on access approval affordance 1236.As shown in FIG. 12F, in response to detecting tap gesture 1238, device605 displays access confirmation interface 1240. In some embodiments,access confirmation interface 1240 is overlaid on access authorizationinterface 1233.

Access confirmation interface 1240 includes continue affordance 1240 aand cancel affordance 1240 b. In response to selection of cancelaffordance 1240 b, device 605 ceases to display access confirmationinterface 1240 and, optionally, terminates the process for authorizingthe service to access data. In response to selection of continueaffordance 1240 a, device 605 authorizes the service (and device 603,using the service) to access data associated with the user account. Insome embodiments, the service is authorized to access data for apredetermined amount of time. In the illustrated example, for instance,the service has been authorized at 12:00 PM to access data for 1 hour.

In some embodiments, the service cannot yet access data even whenauthorized to access the data. For example, in some embodiments, theservice accesses data only after receiving a request for data (e.g.,from device 603). In response to the request for data, the serviceretrieves the necessary decryption key from device 605 to access thedata, decrypts the data using the decryption key to access the data, andin turn provides the data (e.g., to device 603) in response to therequest. Device 605 provides decryption key(s) in this manner during thetime in which the service is authorized to access data.

In some embodiments, data for a user account is encrypted based on datatype. For example, photos data may be encrypted using a first key andcalendar data may be encrypted using a second key. Accordingly, in someembodiments, the service accesses data based on the type of data beingaccessed. By way of example, if a request to access data is directed tophotos data, the service retrieves a decryption key for photos data, andif a request to access data is directed to files data, the serviceretrieves a decryption key for files data. Because a user may request toaccess multiple data types, the service may retrieve multiple decryptionkeys while authorized to access data.

Once the service has been authorized to access data, device 603 maythereafter (e.g., for a given session, for a given period of time) beused to access user data. For example, while displaying confirmationinterface 1227, device 603 detects selection of acknowledgementaffordance 1228. The selection is a user input 1244 (e.g., mouse click)on the acknowledgement affordance 1228. In response to user input 1244,device 603 displays data interface 1246, as shown in FIG. 12G.

Data interface 1246 includes data affordances 1250 a-k, each of whichcorresponds to a respective data type. For example, data affordance 1250a corresponds to a mail data type, data affordance 1250 b corresponds tocontacts data, data affordance 1250 c corresponds to calendar data, dataaffordance 1250 d corresponds to photos data, data affordance 1250 ecorresponds to videos data, data affordance 1250 f corresponds to notesdata, data affordance 1250 g corresponds to task data, data affordance1250 h corresponds to files data, data affordance 1250 i corresponds tonumbers data, data affordance 1250 j corresponds to presentation data,and data affordance 1250 k corresponds to device geolocation data.

Each data affordance 1250 may be used to access data of thecorresponding type. For example, while displaying the data interface1246, device 603 detects selection of data affordance 1250 hcorresponding to files data. The selection is a user input 1252 (e.g.,mouse click) on the data affordance 1250 h. In response to selection ofdata affordance 1250 h, at 12:01 PM, device 603 provides a request tothe service for access to files data for the user account. Because, at12:01 PM the service is authorized to access data (recall that theservice was authorized at 12:00 PM for 1 hour), in turn, the serviceretrieves the decryption key for files data from device 605, decryptsthe data using the decryption key, and provides the requested files datato device 603.

In some embodiments, upon providing the decryption key to the service,device 605 indicates that access has been provided to the service. Withreference to FIG. 12G, device 605 displays notification 1248 indicatingthat the service has been provided with access to files data.

Thereafter, other types of data may be accessed so long as the serviceis authorized to access data. For example, in FIG. 8H, while displayingthe data interface 1246, device 603 detects selection of data affordance1250 d corresponding to photos data. The selection is a user input 1256(e.g., mouse click) on the data affordance 1250 d. In response toselection of data affordance 1250 d, at 12:11 PM, device 603 provides arequest to the service for access to photos data for the user account.Because, at 12:11 PM the service is authorized to access data (recallthat the service was authorized at 12:00 PM for 1 hour), the serviceretrieves the decryption key for photos data from device 605, decryptsthe data using the decryption key, and provides the requested photosdata to device 603. Additionally, device 605 displays notification 1254indicating that the service has been provided with access to photosdata.

In some embodiments, the service can access data even after the serviceis no longer authorized to access data. For example, in FIG. 8I, whiledisplaying the data interface 1246, device 603 detects selection of dataaffordance 1250 d corresponding to photos data. The selection is a userinput 1258 (e.g., mouse click) on the data affordance 1250 d. Inresponse to selection of data affordance 1250 d, at 1:02 PM, device 603provides a request to the service for access to photos data for the useraccount. Although the service is no longer authorized to access data at1:02 PM (recall that the service was authorized at 12:00 PM for 1 hour),the service is still in possession of the decryption key for photosdata, and can provide photos data in response to the request provided bydevice 603. In some embodiments, the service retains keys in this mannerfor the time in which the user remains authenticated by the service.

In some embodiments, the time for which the service is authorized may beextended and/or renewed. With further reference to FIG. 8I, whiledisplaying the data interface 1246, device 603 detects selection of dataaffordance 1250 i corresponding to numbers data. The selection is a userinput 1260 (e.g., mouse click) on the data affordance 1250 i. Inresponse to selection of data affordance 1250 d, at 1:02 PM, device 603provides a request to the service for access to numbers data for theuser account. Because the service is no longer authorized to accessdata, device 605 does not provide the service with a decryption keynecessary to access the numbers data for the user account. Rather,device 605 displays a notification 1262 which, when selected, promptsthe user to authorize (e.g., re-authorize) the service to access dataassociated with the user account, as described.

In some embodiments, a subset of data types do not require authorizationto be accessed or may be accessed without fully authenticating a userwith two-factor authentication. In FIG. 8J, for instance, device 603displays data interface 1263 in an example in which the service has notbeen authorized to access data. As shown, data affordances 1250 d-j aredisplayed with indicators 1264, indicating that data types associatedwith data affordances 1250 d-j, respectively, require authorization tobe accessed. Data affordances 1250 a-c,k are not displayed with anindicator, indicating that data types associated with data affordances1250 a-c,k do not require authorization to access. For example, whiledisplaying data interface 1263, device 603 detects selection of dataaffordance 1250 k corresponding to device geolocation data. Theselection is a user input 1269 (e.g., mouse click) on data affordance1250 k. As shown in FIG. 12K, in response to selection of dataaffordance 1250 k, device 603 displays map interface 1270 correspondingto the requested device geolocation data.

FIG. 13 is a flow diagram illustrating a method for managing data accessusing a computer system in accordance with some embodiments. Method 1300is performed at a computer system (e.g., 100, 300, 500, 600, 603, 605)(e.g., a personal computer, a tablet, a smartphone) that is incommunication with a display generation component (e.g., a television, adisplay controller, an internal or external touch-sensitive displaysystem) and one or more input devices (e.g., a touch-sensitive surface,a mouse, a keyboard). Some operations in method 1300 are, optionally,combined, the orders of some operations are, optionally, changed, andsome operations are, optionally, omitted.

As described below, method 1300 provides an intuitive way for managingdata access. The method reduces the cognitive burden on a user formanaging data access, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user tomanage data access faster and more efficiently conserves power andincreases the time between battery charges.

After displaying, via the display generation component (609), data of afirst type (e.g., photos, contacts, notes, calendar), the computersystem (e.g., 603) receives (1302), via the one or more input devices, arequest (e.g., 1256, 1258, 1260, 1269) to display respective data. Insome embodiments, the request is a user input (e.g., 1256, 1258, 1260,1269), such as a mouse click. In some embodiments, the request to accessdata is selection of an affordance (e.g., 1250 a-k), for instance, on atouch-sensitive display. In some embodiments, the selected affordance isa set of affordances that correspondence to a set of data types,respectively.

In response to receiving the request to display the respective data(1304), in accordance with a determination that the request to displaythe respective data satisfies access criteria, the computer systemdisplays (1306) the requested respective data (e.g., displaying therequested respective data regardless of whether the respective data isdata of a specific type). In some embodiments, the access criteriaincludes a requirement that the request (e.g., 1256, 1258, 1260, 1269)is received by the computer system within a time window. In someembodiments, the time window is defined by a time at which a user hasauthorized to access data including the requested data and apredetermined amount of time. In some embodiments, the time window is 1hour in length.

In response to receiving the request to display the respective data(1304), in accordance with a determination that the request to displaythe respective data does not satisfy the access criteria (1308), inaccordance with a determination that the request to display therespective data is a request to display data of the first type, thecomputer system displays (1310) (e.g., receives, accesses), via thedisplay generation component, the requested respective data. In someembodiments, the computer system displays requested data if therequested data is a same type as previously displayed data, regardlessif the access criteria is met. In some embodiments, prior to thecomputer system displaying data, a remote server hosting the datareceives a key for accessing the data of the first type and cansubsequently provide the data of the first type to the computer systemsuch that the computer system can thereafter display the data of thefirst type regardless of whether access criteria is met.

In response to receiving the request to display the respective data(1304), in accordance with a determination that the request to displaythe respective data does not satisfy the access criteria (1308), inaccordance with a determination that the request to display therespective data is not a request to display data of the first type(e.g., the request is a request to display data of a second type,different than the first type), the computer system initiates (1312) aprocess to display a first notification (e.g., 1230) on an externaldevice (e.g., 605) (e.g., mobile device) for providing the computersystem access to the requested respective data. In some embodiments,initiating the process includes transmitting a set of instructions tothe external device (e.g., 605) and/or to a another device (e.g., acommunication server) in communication with the external device. In someembodiments, selection of the notification (e.g., 1230) at the externaldevice initiates a process for providing the computer system access tothe respective data (e.g., as described with reference to FIGS. 12D-F).In some embodiments, providing the computer system access to the data ofthe respective data includes providing a second external device (e.g.,server hosting the data) access to the respective data. In someembodiments, the second external device is provided with the necessarydecryption mechanism (e.g., decryption key) to access encrypted datasuch that the server provides unencrypted data to the computer system.In some embodiments, a decryption mechanism is provided for each datatype accessed by the computer system. Displaying requested data of aparticular type when a request to display the requested data does notmeet access criteria allows a user to retrieve previously accessed datawithout additional authentication and/or authorization, which reducesthe number of inputs needed to perform an operation.

In some embodiments, the access criteria includes a criterion that ismet when the request (e.g., 1256, 1258, 1260, 1269) to display therespective data is received within a predetermined amount of time (e.g.,1 hour) after the computer system has been authorized to access therespective data. In some embodiments, the external device (e.g., 605) isused to provide the computer system with access (e.g., authorize thecomputer system to access) the requested data. In some embodiments, theexternal device provides access to the computer system in response to aset of one or more inputs (e.g., 1232, 1238, 1242). Authorizing thecomputer system to access data for a predetermined amount of time allowsfor a user to access multiple types of data without a need to authorizefor each access, which reduces the number of inputs needed to perform anoperation.

In some embodiments, prior to displaying the data of the first type, thecomputer system receives a request to display the data of the first type(e.g., 1256, 1258, 1260, 1269). In some embodiments, in response toreceiving the request to display the data of the first type, thecomputer system initiates a process to display a second notification(e.g., 1230) on the external device (e.g., mobile device) for providingthe computer system access to the data of the first type. In someembodiments, selection of the notification at the external deviceinitiates a process for providing the computer system access to the dataof the first type (e.g., as described with reference to FIG. 12G. Insome embodiments, providing the computer system access to the data ofthe first type includes providing a second external device (e.g., serverhosting the data) access to the data of the first type (e.g., the serveris provided with the necessary decryption mechanism (e.g., decryptionkey) to access encrypted data such that the server provides unencrypteddata to the computer system. In some embodiments, a decryption mechanismis provided for each data type accessed by the computer system.

In some embodiments, the first notification (e.g., 1230), when selected,initiates a process (e.g., a process at the external device, thecomputer system, and/or a second external device (e.g., a server)) forproviding the computer system access to the requested respective data.In some embodiments, the process includes prompting (e.g., withnotification 1230 of interface 1229) a user to provide input allowing ordenying the computer system access to the respective data. In someembodiments, the process includes displaying a set of one or more userinterfaces (e.g., interfaces including notifications 1248, 1254)indicating the manner in which access is provided and/or types of datato which access is provided. By way of example, access may be providedto the computer system such that the respective data may be accessedusing web browser and/or first-party applications. As another example,access may be provided for a subset of a set of data types or for alldata types (e.g., data types corresponding to data affordances 1250a-k).

In some embodiments, after displaying the requested respective data, thecomputer system initiates a process to display a third notification(e.g., 1248, 1254) on the external device indicating that the computersystem has been provided access to the requested respective data. Insome embodiments, the notification (e.g., 1248, 1254) indicating thatthe computer system has been provided access to the requested respectivedata is displayed after the computer system has accessed the requestedrespective data. In some embodiments, the notification (e.g., 1248,1254) indicates one or more types of data accessed by the computersystem. Displaying a notification on an external device to indicate thatthe computer system has been provided access provides the user withvisual feedback regarding whether the computer system has been providedaccess to data, which provides improved visual feedback.

In some embodiments, prior to displaying the data of the first type, thecomputer system initiates a process to authenticate a user of thecomputer system (e.g., authenticate an identity of a user of thecomputer system) using the external device (e.g., as described withreference to FIGS. 12A-B). In some embodiments, accessing the data ofthe first type and/or the requested respective data requires that a userof the computer system be authenticated using one or more knownauthentication schemes, such as two-factor authentication. In someembodiments, the user of the computer system is authenticated with theexternal device, for instance, using an authentication code provided(e.g., received, displayed, generated) by the external device. In someembodiments, the external device receives the authentication code via adata messaging application and/or an SMS protocol. In some embodiments,if the authentication code is received via the SMS protocol, theauthentication code may be used to authenticate the computer system suchthat the computer system has access to a predetermined set of data types(e.g., mail, contacts, calendar, and/or device geolocation data). Insome embodiments, the set of predetermined set of data types is a subsetof data types that would otherwise be accessed by the computer system ifthe authentication code were not received via the SMS protocol. In someembodiments, the computer system is authenticated in response to a userauthenticating with the external device using biometric (e.g., facial,fingerprint, iris) authentication. In some embodiments, further prior todisplaying data of first type, the computer system initiates a processfor checking web access permissions. In some embodiments, the processincludes checking (using the computer system and/or external device)whether web access is enabled for an account of the user of the computersystem. In some embodiments, if web access is disabled, the externaldevice displays a notification requesting user approval for web accessby the computer system.

In some embodiments, the computer system displays, via the displaygeneration component, a data access interface (e.g., 1246, 1263). Insome embodiments, the data access interface includes an affordance(e.g., 1250 a-k) for each data type for which the computer system mayrequest access. In some embodiments, the data access interface includesa first affordance (e.g., 1250 a-k) corresponding to the data of thefirst type (e.g., mail, contacts, calendar, device geolocation data). Insome embodiments, selection of the first affordance causes the computersystem to display data of the first type. In some embodiments, the dataaccess interface includes a second affordance (e.g., 1250 a-k)corresponding to data of a second type (e.g., photos, notes, files),where the second type is different than the first type. In someembodiments, selection of the second affordance causes the computersystem to selectively display data of the second type. In someembodiments, the computer system displays data of the second type whenthe computer system has been authorized to access the data of the secondtype. In some embodiments, the first affordance has a first displaycharacteristic (e.g., lack of indicator 1264) indicating that thecomputer system has been provided access to the data of the first type.In some embodiments, if the computer system has been provided access todata of the first type, the first affordance is displayed without anindicator (e.g., lock icon) indicating that the computer system has notbeen provided access to the first data type. In some embodiments, thesecond affordance has a second display characteristic (e.g., 1264),different than the first display characteristic, indicating that thecomputer system has not been provided access to the data of the secondtype. In some embodiments, if the computer system has not been providedaccess to data of the second type, the second affordance is displayedwith an indicator (e.g., lock icon) indicating that the computer systemhas not been provided access to the second data type. Displaying a dataaccess interface with a first affordance and a second affordancecorresponding to respective data types in this manner allows a user toquickly and efficiently select a data type to access, which reduces thenumber of inputs needed to perform an operation.

In some embodiments, providing an indication that the computer system isauthorized to access data includes authenticating (e.g., biometricallyauthenticating), using the external device, a user of the user account.

In some embodiments, the request to display the respective datasatisfies access criteria when the respective data includes (e.g., onlyincludes) unsecured data (e.g., mail, contacts, calendar, devicegeolocation data) (e.g., as described with reference to FIG. 12J).

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 11 ) are also applicable in an analogous mannerto the methods described below. For example, method 1100 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 1300. For example, disablingweb access to data, as described in method 900, may cause the computersystem and/or one or more external devices to selectively limit accessto data based on access criteria, as described in method 1300. Forbrevity, these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve themanner in which users access accounts. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter IDs, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toauthenticate users during account recovery processes. Accordingly, useof such personal information data enables users to access authorizedaccounts. Further, other uses for personal information data that benefitthe user are also contemplated by the present disclosure. For instance,health and fitness data may be used to provide insights into a user'sgeneral wellness, or may be used as positive feedback to individualsusing technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof account recovery, the present technology can be configured to allowusers to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In addition to providing “opt in” and “opt out”options, the present disclosure contemplates providing notificationsrelating to the access or use of personal information. For instance, auser may be notified upon downloading an app that their personalinformation data will be accessed and then reminded again just beforepersonal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, account accessmay be provided based on non-personal information data or a bare minimumamount of personal information, such as a password associated with auser, other non-personal information available to the accountauthentication services, or publicly available information.

What is claimed is:
 1. A computer system configured to communicate witha display generation component and one or more input devices,comprising: one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors, theone or more programs including instructions for: performing a recoverycontact set up process including providing a notification to a contact;after performing the recovery contact set up process, receiving, via theone or more input devices, a request to initiate an account recoveryprocess via the contact; in response to the request to initiate theaccount recovery process via the contact and without providing a requestto the contact, displaying, via the display generation component, arecovery code interface for receiving a set of recovery credentials;while displaying of the recovery code interface, receiving the set ofrecovery credentials; in accordance with a determination that therecovery credentials are valid, performing a recovery function; and inaccordance with a determination that the recovery credentials are notvalid, forgoing performing the recovery function.
 2. The computer systemof claim 1, wherein the computer system is associated with a user,wherein performing the recovery contact set up process includesauthenticating, via the one or more input devices, the user.
 3. Thecomputer system of claim 1, wherein: performing the recovery contact setup process includes: receiving a first user input corresponding to thecontact; and in response to receiving the first user input and inaccordance with a determination that the contact is a contact of a firsttype, adding the contact as a recovery contact; and providing thenotification to the contact occurs in response to receiving the firstuser input.
 4. The computer system of claim 3, wherein providing thenotification to the contact includes: in response to the first userinput and in accordance with a determination that the contact is not acontact of the first type, providing a request to the contact to add thecontact as a recovery contact, without adding the contact as a recoverycontact in response to the first user input.
 5. The computer system ofclaim 4, the one or more programs further including instructions for:after providing the request to the contact to add the contact as arecovery contact, receiving, from the contact, an approval of therequest to add the contact as a recovery contact; and in response toreceiving the approval, adding the contact as a recovery contact.
 6. Thecomputer system of claim 1, wherein performing the recovery contact setup process includes initiating the recovery contact set up process, theone or more programs further including instructions for: afterinitiating the recovery contact set up process, displaying a recoverysettings interface that includes: a first recovery contact graphicalobject that corresponds to a first recovery contact that is authorizedto receive the set of recovery credentials for use in the recoveryfunction; and a first recovery contactee graphical object that indicatesa second contact that a user of the computer system is authorized toassist with a second recovery function.
 7. The computer system of claim1, the one or more programs further including instructions for: prior todisplaying the recovery code interface, displaying, via the displaygeneration component, an authentication interface that includes a set ofone or more user-interactive graphical user interface objects forauthenticating a user of the computer system; receiving a first set ofone or more user inputs that includes a second user input that isreceived while displaying the authentication interface; and in responseto receiving the first set of one or more user inputs, ceasing todisplay the authentication interface, without authenticating a user ofthe computer system, wherein the first set of one or more user inputs isthe request to initiate the account recovery process.
 8. The computersystem of claim 7, wherein: the authentication interface includes aforgot passcode user-interactive graphical user interface object that,when selected, causes the authentication interface to cease beingdisplayed without authenticating a user of the computer system; and thesecond user input corresponds to the forgot passcode user-interactivegraphical user interface object.
 9. The computer system of claim 7,wherein the first set of one or more user inputs includes a third userinput, the one or more programs further including instructions for: inresponse to the third user input, displaying a help user interface thatincludes an ask for help user-interactive graphical user interfaceobject; wherein: the third user input corresponds to the ask for helpuser-interactive graphical user interface object.
 10. The computersystem of claim 7, wherein the first set of one or more user inputsincludes a fourth user input, the one or more programs further includinginstructions for: after ceasing to display the authentication interface,without authenticating a user of the computer system, displaying aplurality of device user-interactive graphical user interface objectsthat corresponds to external electronic devices associated with thecontact; wherein the fourth user input corresponds to a first deviceuser-interactive graphical user interface object of the plurality ofdevice user-interactive graphical user interface objects thatcorresponds to a first external electronic device associated with thecontact.
 11. The computer system of claim 10, the one or more programsfurther including instructions for: in response to the fourth userinput, displaying: in accordance with a determination that the firstexternal electronic device is a device of a first type, a first set ofinstructions for providing the set of recovery credentials on the firstexternal electronic device; and in accordance with a determination thatthe first external electronic device is a device of a second type, asecond set of instructions, different from the first set ofinstructions, for providing the set of recovery credentials on the firstexternal electronic device.
 12. The computer system of claim 1, whereinthe account recovery process is performed for a user account and whereinperforming the recovery function includes initiating a password changeprocess for the user account.
 13. The computer system of claim 1, theone or more programs further including instructions for: receiving, froma first external computer system, a request for a user of the computersystem to be added as a recovery contact for the first external computersystem; and in response to receiving the request for the user of thecomputer system to be added as a recovery contact for the first externalcomputer system, displaying an acceptance user-interactive graphicaluser interface object; receiving a user input corresponding to theacceptance user-interactive graphical user interface object; and inresponse to receiving the user input corresponding to the acceptanceuser-interactive graphical user interface object, transmitting, to thefirst external computer system, an indication that the request wasaccepted.
 14. The computer system of claim 13, the one or more programsfurther including instructions for: after transmitting, to the firstexternal computer system, the indication that the request was accepted,receiving a second set of one or more user inputs; and in response toreceiving the second set of one or more user inputs, providing a secondset of recovery credentials that, when entered at the first externalcomputer system, enables a second recovery function.
 15. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: performing a recovery contact set up processincluding providing a notification to a contact; after performing therecovery contact set up process, receiving, via the one or more inputdevices, a request to initiate an account recovery process via thecontact; in response to the request to initiate the account recoveryprocess via the contact and without providing a request to the contact,displaying, via the display generation component, a recovery codeinterface for receiving a set of recovery credentials; while displayingof the recovery code interface, receiving the set of recoverycredentials; in accordance with a determination that the recoverycredentials are valid, performing a recovery function; and in accordancewith a determination that the recovery credentials are not valid,forgoing performing the recovery function.
 16. A method, comprising: ata computer system in communication with a display generation componentand one or more input devices: performing a recovery contact set upprocess including providing a notification to a contact; afterperforming the recovery contact set up process, receiving, via the oneor more input devices, a request to initiate an account recovery processvia the contact; in response to the request to initiate the accountrecovery process via the contact and without providing a request to thecontact, displaying, via the display generation component, a recoverycode interface for receiving a set of recovery credentials; whiledisplaying of the recovery code interface, receiving the set of recoverycredentials; in accordance with a determination that the recoverycredentials are valid, performing a recovery function; and in accordancewith a determination that the recovery credentials are not valid,forgoing performing the recovery function.